Static findings are false positives caused by Markdown code fences, inline file path formatting, and a pricing table header. I found no executable command instructions, prompt injection text, data exfiltration intent, or system reconnaissance behavior in SKILL.md.
Static findings are false positives caused by Markdown code fences, inline file path formatting, and a pricing table header. I found no executable command instructions, prompt injection text, data exfiltration intent, or system reconnaissance behavior in SKILL.md.
AI review found the static detections are false positives in documentation-only Markdown. Backticks are examples or reference file names, weak cryptography hits are substring matches, and no executable code, data exfiltration, prompt injection, or malicious intent was found.
False positive: Markdown backticks flagged as shell execution
The flagged locations are Markdown code fences, ASCII diagrams, templates, and inline reference file names. They do not invoke Ruby, a shell, or any executable command path.
Each flagged backtick appears in Markdown documentation or inline file references. No surrounding text defines a script, runtime command, or user-controlled command execution path.
False positive: Weak cryptography detector matched ordinary text
The flagged lines contain skill metadata and a product differentiation bullet. They do not reference DES, MD5, SHA-1, or any cryptographic implementation.
The surrounding context is business strategy prose, not software security logic. No cryptographic API, algorithm selection, hashing, or encryption behavior is present.
False positive: System reconnaissance detector matched a pricing table
The flagged line is a Markdown pricing comparison table header. It does not collect host details, enumerate system state, or run reconnaissance commands.
The line is visibly part of a competitor pricing matrix. There is no command, file access, environment access, or system information collection behavior.
Static analysis flagged markdown documentation as security issues. All findings are false positives: backticks are markdown code block delimiters, not shell execution; YAML frontmatter and table content were misinterpreted. This is pure documentation with no code execution, network access, or system interaction.
Static scanner detected backticks as command execution. These are markdown code block fences, not Ruby/shell backticks.
All 13 locations contain markdown triple-backtick code block delimiters (```), not Ruby/shell backtick execution. This is standard markdown syntax for code examples.