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.
npx agentmods add commands/fusengine/agents/scangit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/scan)<a href="https://agentmods.dev/commands/fusengine/agents/scan"><img src="https://agentmods.dev/badge/commands/fusengine/agents/scan.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00485 |
| Opus 5 | $0.00015 | $0.00243 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
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 yesterday.
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
Security Scan
Execute a comprehensive security audit following the 5-phase workflow.
Usage
/scan- Full security audit of current project/scan --deps-only- Dependency audit only/scan --headers- Security headers check only/scan --auth- Authentication patterns audit only/scan path/to/dir- Scan specific directory
Workflow
Phase 1: DETECT
Identify project language and framework automatically:
- Scan for marker files (package.json, composer.json, etc.)
- Detect framework versions and dependencies
- Map to appropriate scan patterns
Phase 2: RESEARCH
Query recent CVEs for the detected stack:
- Use Exa to search NVD, OSV.dev, GitHub Advisory
- Focus on dependencies found in project
- Check for known exploits
Phase 3: SCAN
Run vulnerability patterns and dependency audit:
- Execute language-specific grep patterns (OWASP Top 10)
- Run
bun ${CLAUDE_PLUGIN_ROOT}/../node_modules/@fusengine/harness/dist/cli/bin.mjs scan <dir>for automated pattern matching - Execute dependency audit CLI (npm audit, composer audit, etc.)
- Detect hardcoded secrets and credentials
Phase 4: REPORT
Generate structured vulnerability report:
- Categorize by severity: CRITICAL, HIGH, MEDIUM, LOW
- Map findings to OWASP A01-A10 categories
- Include file:line references and fix instructions
Phase 5: FIX
Delegate corrections to sniper agent:
- Generate fix instructions per vulnerability
- Invoke sniper with precise file:line + description
- Validate all fixes applied correctly
Arguments
$ARGUMENTSspecifies scan options and target path
Examples
/scan→ Full OWASP + dependency + secrets audit/scan --deps-only→ Quick dependency vulnerability check/scan --auth→ JWT/OAuth/session security patterns/scan src/api/→ Scan only API directory
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.
- yesterday First seen · 62 lines · 30 tokens per session scan A b31fe0f940ac
scan is a command published in the GitHub repository fusengine/agents (25 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 485 once invoked, about $0.0002 per session on Opus 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-03.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.