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/ofershap/vibe-guard/security-auditgit clone --depth 1 https://github.com/ofershap/vibe-guardWhat 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.00016 | $0.00247 |
| Opus 5 | $0.00008 | $0.00123 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
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 3d 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
Perform a comprehensive security audit of this project:
-
Secrets scan: Search all files for hardcoded API keys, passwords, tokens, connection strings. Check .env files are in .gitignore.
-
Input validation: Find all API endpoints and check if user input is validated before processing.
-
Authentication: Check if all non-public routes have authentication middleware.
-
Database security: Check for SQL injection vulnerabilities, missing RLS policies, unparameterized queries.
-
CORS configuration: Check if CORS is properly restricted (not wildcard).
-
Error handling: Check if error responses leak internal details (stack traces, DB errors).
-
Dependencies: Check for known vulnerabilities in dependencies.
-
Headers: Check if security headers are set (CSP, HSTS, X-Frame-Options).
For each issue found:
- Show the file and line
- Explain the vulnerability
- Show the fix
- Rate severity: CRITICAL / HIGH / MEDIUM / LOW
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.
- 3d ago First seen · 33 lines · 16 tokens per session scan A ef5491a84165
security-audit is a command published in the GitHub repository ofershap/vibe-guard (1 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 247 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
loop
Iteratively fix issues until all resolved or max iterations reached.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
VibeGuard: Cross Review
Dual-model adversarial review — Claude generates review reports, Codex does adversarial verification, and iterates until convergence.