Audit History

Most static alerts are Markdown formatting false positives, including endpoint names, prompt examples, and API path placeholders. I confirmed intended RunComfy CLI commands and outbound Model API requests. They execute local tools and send user data to RunComfy. No prompt injection text or covert malicious intent was found in SKILL.md.

Most static alerts are Markdown formatting false positives, including endpoint names, prompt examples, and API path placeholders. I confirmed intended RunComfy CLI commands and outbound Model API requests. They execute local tools and send user data to RunComfy. No prompt injection text or covert malicious intent was found in SKILL.md.

The review confirmed documented RunComfy CLI execution, a POST to the RunComfy Model API, and local RunComfy token storage. Most other detections are Markdown formatting, example placeholders, REST path abbreviations, or sample prompts with no execution behavior. No prompt injection or covert data exfiltration intent was found.

The review confirmed documented RunComfy CLI execution, a POST to the RunComfy Model API, and local RunComfy token storage. Most other detections are Markdown formatting, example placeholders, REST path abbreviations, or sample prompts with no execution behavior. No prompt injection or covert data exfiltration intent was found.

Static analysis correctly found external command, network, and filesystem indicators, but most individual hits are Markdown backticks, command examples, URL placeholders, or prose. No prompt injection or confirmed malicious intent was found; the real risk is that the skill directs users to run the RunComfy CLI, send prompts and image URLs to RunComfy endpoints, store or provide a bearer token, and write generated files locally.

Static analysis flagged 77 patterns across SKILL.md (58 shell backticks, 10 hardcoded URLs, 5 filesystem paths, 3 weak-crypto indicators, 1 reconnaissance). All findings evaluated as false positives: backticks contain markdown CLI documentation examples, URLs are legitimate RunComfy service endpoints, filesystem references document CLI config paths (~/.config/runcomfy/token.json), and crypto/reconnaissance patterns are misidentified text ("Exit codes" heading, jq pipe examples). No executable code, no prompt injection, no data exfiltration detected. Minor concerns: user prompts transmitted to RunComfy's external API, third-party CLI dependency, local token file storage.