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/WebDevPeterGriffin/The-VibeCode-BibleWrote 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/rules/webdevpetergriffin/the-vibecode-bible/astro-build-and-deployment)<a href="https://agentmods.dev/rules/webdevpetergriffin/the-vibecode-bible/astro-build-and-deployment"><img src="https://agentmods.dev/badge/rules/webdevpetergriffin/the-vibecode-bible/astro-build-and-deployment.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.00000 | $0.00084 |
| Opus 5 | $0.00000 | $0.00042 |
| Sonnet 5 | $0.00000 | $0.00017 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
astro-build-and-deployment 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 4d 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.
- 4d ago First seen · 10 lines · 0 tokens per session scan A 9fc22e9f9c47
astro-build-and-deployment is a cursor rule published in the GitHub repository WebDevPeterGriffin/The-VibeCode-Bible (40 stars, last pushed 2mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 84 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 cursor rules, from other repositories
sonnet
Next.js Development for Coding Agent.
frontend
TypeScript Next.js View Component Development Rules.
ui-components
Cursor rule "ui-components" from FluroAsh/nextjs-mdx-portfolio, covering ui components and styling, component libraries, shadcn/ui, custom components and styling approach.
ui-components
Cursor rule "ui-components" from muzaffar640/commitpress, covering ui components, component organization, ui component guidelines, component examples and button component.
nextjs-structure
Cursor rule "nextjs-structure" from Mithgroth/fakestore-mcp, covering project structure, file naming conventions, next.js best practices and component organization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.