Borrowing it
Nothing to install: this file belongs to squirrelsoft-dev/dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/squirrelsoft-dev/dev/main/.claude/commands/security-scan.mdgit clone --depth 1 https://github.com/squirrelsoft-dev/devWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/squirrelsoft-dev/dev/security-scan)<a href="https://agentmods.dev/commands/squirrelsoft-dev/dev/security-scan"><img src="https://agentmods.dev/badge/commands/squirrelsoft-dev/dev/security-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/squirrelsoft-dev/dev/security-scan"><img src="https://agentmods.dev/badge/commands/squirrelsoft-dev/dev/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00262 |
| Opus 5.5 | $0.00004 | $0.00105 |
| Sonnet 5.5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
security-scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Deep Security Scan
Run a comprehensive security analysis of the project. This is the thorough version — use for pre-deploy or periodic audits.
Steps
Run each tool that is available (skip any that aren't installed):
- Gitleaks — full repo history:
gitleaks detect --source=. --verbose - Semgrep — SAST with extended rules:
semgrep --config=auto --config=p/owasp-top-ten - npm audit — full dependency tree:
npm audit - Trivy — filesystem scan:
trivy fs --severity HIGH,CRITICAL . - Knip — dead code and unused deps:
npx knip - Madge — circular dependencies:
npx madge --circular --extensions ts src/
Output
Summarize findings grouped by severity:
- 🔴 Critical — blocks deployment, must fix immediately
- 🟡 High — should fix before next release
- 🟢 Medium/Low — track and address when convenient
Include specific file locations, line numbers, and remediation steps for each finding.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 28 lines · 10 tokens per session scan A 39f5a771eaf6
security-scan is a command published in the GitHub repository squirrelsoft-dev/dev (17 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 262 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.