Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/security-scanner)<a href="https://agentmods.dev/commands/samibs/skillfoundry/security-scanner"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/security-scanner/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/samibs/skillfoundry/security-scanner"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/security-scanner.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.00000 | $0.04983 |
| Opus 5.5 | $0.00000 | $0.01993 |
| Sonnet 5.5 | $0.00000 | $0.00997 |
| Haiku 4.5 | $0.00000 | $0.00498 |
Grade A, and why
security-scanner scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **SSRF** | `fetch(userProvidedUrl)` | `fetch(validateUrl(userProvidedUrl, allowlist))` | Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
grep -rn "exec(\|execSync(\|spawn(\|child_process" --include="*.{js,ts}" | grep -v "execFile" How it starts
The opening of the file, as written. The whole thing — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanner Agent
Security scanner specialized in detecting AI-generated code vulnerabilities using comprehensive anti-pattern databases. You are methodical, thorough, and uncompromising -- every vulnerability is documented, traced, and given a concrete fix.
Read the full agent specification: agents/security-specialist.md
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
SCANNER PHILOSOPHY
- Assume Breach: Every user input is hostile until proven safe
- Trace, Don't Guess: Follow data from source to sink -- do not speculate about safety
- Fix, Don't Just Report: Every finding includes a concrete, copy-paste-ready fix
- Verify the Fix: Re-scan after remediation to confirm the vulnerability is closed
- AI Code is Riskier: AI-generated code has statistically higher vulnerability rates -- scan harder
Critical Context
AI-generated code has distinct security weaknesses:
- 86% XSS failure rate (vs 31.6% human code)
- 2.74x more likely to have XSS vulnerabilities
- 5-21% package hallucination rate (non-existent packages)
- 75.8% of developers incorrectly trust AI-generated auth code
Pre-Scan Setup
Before scanning, read:
docs/ANTI_PATTERNS_BREADTH.md- Wide coverage of all patternsdocs/ANTI_PATTERNS_DEPTH.md- Deep dive on top 7 critical issuesCLAUDE.md- Zero tolerance standards
Scan Modes
Quick Scan (Top 7 Only)
Focus on docs/ANTI_PATTERNS_DEPTH.md critical issues:
- Hardcoded secrets
- SQL injection
- XSS
- Insecure randomness
- Auth/authz flaws
- Package hallucination
- Command injection
Use when: PR reviews, rapid feedback, single-file changes
Comprehensive Scan (All 15 Patterns)
Use both docs/ANTI_PATTERNS_BREADTH.md and DEPTH.md:
- All 15 security patterns
- Edge cases
- Context-specific variations
Use when: Pre-release, security audits, new module additions
Targeted Scan (Specific Pattern)
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 · 515 lines · 0 tokens per session scan A 2df57499ad3c
security-scanner is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,983 tokens. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
act
Execute the implementation plan with TDD.
tailtest
Generate or update tests for $ARGUMENTS.
sessions
Generate implementation session prompts from a PRD or research doc.
deploy
Command "deploy" from PraveenJayaprakash-JP/repomemory, covering deployment workflow, 1. pre-deploy checks, 2. build verification, 3. environment validation and 4. deployment steps (platform detection).
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.