security-scan — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited security-scan (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} is the classic direct prompt-injection phrasing. Placed in a skill body that the agent reads as trusted instructions, it tries to make the agent abandon its prior rules and follow whatever comes next — a full system-prompt override.
ignore/disregard/forget … previous instructions sentence.The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Today: !date "+%Y-%m-%d" Branch: !git branch --show-current Project root: !pwd
You are running a focused security scan. Read procedure.md in this skill folder for the full scanning protocol.
This skill covers the most mechanical, portable security concerns:
For deeper analysis (full OWASP systematic review, attack surface mapping, data flow tracing), perform a comprehensive manual security review with project-specific context.
file:line + quoted code~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.