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/production-checkgit clone --depth 1 https://github.com/ofershap/vibe-guardWrote 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/ofershap/vibe-guard/production-check)<a href="https://agentmods.dev/commands/ofershap/vibe-guard/production-check"><img src="https://agentmods.dev/badge/commands/ofershap/vibe-guard/production-check.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.1 | $0.00016 | $0.00232 |
| Opus 5 | $0.00008 | $0.00116 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
production-check 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 5d 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
Run through this production readiness checklist:
- Environment variables: All secrets in env vars? .env in .gitignore? .env.example exists?
- Authentication: All routes protected? Session management implemented?
- Input validation: All user inputs validated? File uploads restricted?
- Database: Parameterized queries? RLS enabled? Connection pooling configured?
- Error handling: Generic errors in production? Structured logging? No console.log of sensitive data?
- Security headers: CSP, HSTS, X-Frame-Options, X-Content-Type-Options set?
- Rate limiting: Auth endpoints rate-limited? API endpoints rate-limited?
- CORS: Specific origins only? No wildcard in production?
- HTTPS: Forced in production? HSTS header set?
- Dependencies: npm audit clean? No known vulnerabilities?
For each item: PASS / FAIL / NOT APPLICABLE with explanation.
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.
- 5d ago First seen · 21 lines · 16 tokens per session scan A 6c4aa715b5d5
production-check 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 232 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.
validate-gap
Analyze implementation gap between requirements and existing codebase.
spec-impl
Execute spec tasks using TDD methodology.
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.
review
Review the current diff for violations of the conventions in AGENTS.md and .cursor/rules/. Report findings ordered by severity; do not fix anything unless asked.