The audit found one confirmed high-risk behavior: the formatter launches npx to execute autocorrect-node, which introduces external package and host-command risk. The remaining findings are false positives caused by documentation syntax, expected file formatting operations, dependency metadata, integrity hashes, or fixed text escapes; no prompt injection or data-exfiltration intent was found.
8
Files scanned
1,908
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
This import supports the formatter's external npx execution path. The behavior is intentional, but running a package through a host process is a real execution and supply-chain risk.
const result = spawnSync(npxCmd, ["autocorrect-node", "--fix", filePath], {
The formatter synchronously launches npx to run autocorrect-node with the user-provided file path. This executes an external package during formatting and creates supply-chain and host-command risk.
Most static matches are false positives from Markdown backticks, help text, and package lockfile integrity hashes. Confirmed risks remain around shell execution of unescaped file paths, unpinned npx package execution, in-place file writes, and hidden configuration reads.
The workflow runs npx commands that can fetch and execute current registry packages during formatting, including bun and autocorrect-node.
Both code and workflow instructions use npx without pinned package versions. That creates a supply-chain execution risk beyond the generic external-command pattern.
Untrusted Hidden Configuration Can Influence Agent Behavior
The skill directs the agent to read project and home EXTEND.md files and apply their settings, which can let repository-local hidden files steer behavior.
The instructions explicitly define hidden configuration locations and say to read, parse, and apply settings. No direct malicious text was found, but the trust boundary is real.
Capability review items (18)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
execSync runs a shell command containing the user-supplied file path. Quoting does not safely handle embedded quotes or shell metacharacters, so command injection is possible.
execSync runs a shell command containing the user-supplied file path. Quoting does not safely handle embedded quotes or shell metacharacters, so command injection is possible.
The imported synchronous file APIs are used below to read and overwrite the target path. This is expected for a formatter but is still real filesystem capability.
The script writes formatted content back to the provided file path. An incorrect or malicious path could overwrite local files within the agent permissions.
test -f "$HOME/.baoyu-skills/baoyu-format-markdown/EXTEND.md" && echo "user"
The skill explicitly checks hidden project and home-directory EXTEND.md paths and applies settings from them. That is real hidden file access outside the requested document.
│ $HOME/.baoyu-skills/baoyu-format-markdown/EXTEND.md │ User home │
The skill explicitly checks hidden project and home-directory EXTEND.md paths and applies settings from them. That is real hidden file access outside the requested document.
Most static matches are false positives from Markdown backticks, help text, and package lockfile integrity hashes. Confirmed risks remain around shell execution of unescaped file paths, unpinned npx package execution, in-place file writes, and hidden configuration reads.
The workflow runs npx commands that can fetch and execute current registry packages during formatting, including bun and autocorrect-node.
Both code and workflow instructions use npx without pinned package versions. That creates a supply-chain execution risk beyond the generic external-command pattern.
Untrusted Hidden Configuration Can Influence Agent Behavior
The skill directs the agent to read project and home EXTEND.md files and apply their settings, which can let repository-local hidden files steer behavior.
The instructions explicitly define hidden configuration locations and say to read, parse, and apply settings. No direct malicious text was found, but the trust boundary is real.
Capability review items (18)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
execSync runs a shell command containing the user-supplied file path. Quoting does not safely handle embedded quotes or shell metacharacters, so command injection is possible.
execSync runs a shell command containing the user-supplied file path. Quoting does not safely handle embedded quotes or shell metacharacters, so command injection is possible.
The imported synchronous file APIs are used below to read and overwrite the target path. This is expected for a formatter but is still real filesystem capability.
The script writes formatted content back to the provided file path. An incorrect or malicious path could overwrite local files within the agent permissions.
test -f "$HOME/.baoyu-skills/baoyu-format-markdown/EXTEND.md" && echo "user"
The skill explicitly checks hidden project and home-directory EXTEND.md paths and applies settings from them. That is real hidden file access outside the requested document.
│ $HOME/.baoyu-skills/baoyu-format-markdown/EXTEND.md │ User home │
The skill explicitly checks hidden project and home-directory EXTEND.md paths and applies settings from them. That is real hidden file access outside the requested document.
Static analysis found many command-like patterns, but most SKILL.md hits are Markdown documentation examples or formatting syntax. One confirmed issue remains: scripts/autocorrect.ts builds a shell command with a user-controlled file path, creating command injection risk. No prompt injection, network exfiltration, environment access, or malicious intent was found.
The skill checks project and home EXTEND.md paths under .baoyu-skills for optional preferences. This is a bounded configuration lookup, but users should know it may read formatter preferences from hidden directories.
The documented paths are narrow and preference-oriented, so this is not secret harvesting. It is still a hidden-file access pattern worth disclosing.
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
scripts/autocorrect.ts imports child_process and passes a template string to execSync. The file path comes from the CLI argument flow in scripts/main.ts, so a crafted path containing quotes or shell metacharacters can break out of the quoted argument and run arbitrary shell commands.
The code directly interpolates a user-supplied file path into an execSync shell command. Quoting the path does not prevent injection when the value can contain quote characters.
The workflow instructs users to run npx with bun and the script invokes npx autocorrect-node. This executes external tooling without a pinned package version in the documented command path, creating supply-chain and reproducibility risk.
The external execution path is explicit and repeatable. The finding is not evidence of malware, but unpinned npx execution is a real marketplace risk.
scripts/main.ts reads and writes the target file directly, and the skill also offers a typography-only mode that modifies the original file. This is expected formatter behavior, but it can overwrite user content if the wrong path is supplied or backup handling is bypassed.
The file read and write behavior is clear in the implementation and documentation. It is legitimate for a formatter, but it has user-data impact.
Static false positives ignored (1)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Most SKILL.md external command findings are Markdown examples, inline code, tables, and fenced commands that document formatter usage. The weak cryptography and reconnaissance alerts did not correspond to cryptographic operations or system probing in the reviewed file.
Line-number review shows documentation content and Markdown syntax, not executable code for cryptography or reconnaissance. The safe interpretation is supported by the surrounding workflow text.
Security evaluation confirms this is a legitimate markdown formatting skill. Static findings flagged external command execution (autocorrect-node), filesystem operations, and npm package URLs. All are false positives: execSync runs a known typography tool with CLI-provided paths, file I/O is scoped to user-specified files, and network access is limited to standard npm package downloads.
SHA-1 hashes detected in npm package-lock.json. These are standard npm integrity verification hashes, not cryptographic vulnerabilities in the skill code.
Standard npm package-lock.json SHA-1 integrity hashes for package verification - not a security vulnerability in the skill itself.
execSync used to run npx autocorrect-node. This is a legitimate typography tool call, not command injection. The filePath argument comes from CLI input and is enclosed in quotes, minimizing injection risk.
This is a false positive - execSync runs a known typography tool (autocorrect-node) with hardcoded command structure. The file path argument is properly quoted.