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/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/security-audit)<a href="https://agentmods.dev/commands/strikersam/autonomous-ai-agency/security-audit"><img src="https://agentmods.dev/badge/commands/strikersam/autonomous-ai-agency/security-audit/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/strikersam/autonomous-ai-agency/security-audit"><img src="https://agentmods.dev/badge/commands/strikersam/autonomous-ai-agency/security-audit.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.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
security-audit 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 8d 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
/security-audit — Security Agent
Perform a targeted security audit of the codebase or a specific module.
When to use
- Before any PR that touches
admin_auth.py,key_store.py,agent/tools.py,rbac.py,social_auth.py, orproxy.pyauth middleware - After adding a new API endpoint
- After adding a new dependency
- On a scheduled basis (monthly)
Steps
-
Read context
- Read
AGENTS.mdsections: Security Requirements, Risky Modules - Read
audit/security-analysis.mdfor known open issues - Run
graphify query "security vulnerabilities"to check known concerns
- Read
-
Dependency audit
pip-audit --requirement requirements.txt --output json > /tmp/pip_audit.json cat /tmp/pip_audit.json -
Static analysis
# Run bandit on the codebase bandit -r . -x .venv,tests,node_modules --severity-level medium -f json -
Hardcoded secrets check
grep -rn --include="*.py" --exclude-dir=.venv --exclude-dir=tests \ 'SECRET_KEY\s*=\s*["\x27][^"]+["\x27]' . -
Auth path review
- Read
proxy.pylines 195-292 (auth middleware) - Read
admin_auth.py - Verify
hmac.compare_digestor equivalent used for secret comparison - Verify rate limiter cannot be bypassed
- Read
-
CORS check
grep -n "CORS_ORIGINS" proxy.pyVerify it's not
*in production. -
Agent filesystem boundary check
- Read
agent/tools.py _resolve_path() - Verify
AGENT_WORKSPACE_ROOTis set and does not equal repo root
- Read
-
Report findings
- Severity: P0 (immediate), P1 (this sprint), P2 (next sprint)
- Create GitHub issues for P0/P1 findings
- Update
audit/security-analysis.mdwith new findings
Escalation
Stop and ask the user before fixing:
- Any P0 security vulnerability (immediate escalation required)
- Any change to risky modules that affects auth flows
- Any change that could break existing authenticated sessions
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.
- 8d ago First seen · 64 lines · 0 tokens per session scan A 5125ba3d22f8
security-audit is a command published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 tokens. 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.