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 rules/webdevpetergriffin/the-vibecode-bible/code-output-rulesgit clone --depth 1 https://github.com/WebDevPeterGriffin/The-VibeCode-BibleWhat 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.00116 | $0.00116 |
| Opus 5 | $0.00058 | $0.00058 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
code-output-rules 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 8 lines · 116 tokens per session scan A 1374128e0afb
code-output-rules is a cursor rule published in the GitHub repository WebDevPeterGriffin/The-VibeCode-Bible (39 stars, last pushed 2mo ago), with no licence file. It adds 116 tokens to every session, about $0.0006 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-30.
Other cursor rules, from other repositories
repo
understanding the structure of the monorepo.
stripe-payments
Stripe payment integration patterns — server-only, webhook handling.
kit-only
Unless a later spec says otherwise, only touch.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
NewGroup
Guidance on how to add details.json files for new social groups.
software-factory
Software factory operating rules.