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/FutureExcited/vibe-rulesWrote 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/futureexcited/vibe-rules/architecture)<a href="https://agentmods.dev/rules/futureexcited/vibe-rules/architecture"><img src="https://agentmods.dev/badge/rules/futureexcited/vibe-rules/architecture/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/rules/futureexcited/vibe-rules/architecture"><img src="https://agentmods.dev/badge/rules/futureexcited/vibe-rules/architecture.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.00082 | $0.00082 |
| Opus 5.5 | $0.00033 | $0.00033 |
| Sonnet 5.5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
architecture 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 1mo 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
At the end of each task, you need to write all changes to ARCHITECTURE.md.
And by write all changes, I mean modify the architecture of the entire app. If you've changed a function - modify its params/output or whatever you changed. If you've added a new file - add it to the ARCHITECTURE.md.
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.
- 1mo ago First seen · 9 lines · 82 tokens per session scan A ba2d9fc38bfa
architecture is a cursor rule published in the GitHub repository FutureExcited/vibe-rules (528 stars, last pushed 1y ago), licensed MIT. It adds 82 tokens to every session, about $0.0003 per session on Opus 5.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
propose-test-cases
Propose comprehensive test cases for PR changes.
detect-code-smells
Detect code smells and anti-patterns in PR changes.
suggest-improvements
Provide actionable improvement suggestions for PR changes.
refactor-test
Review and refactor generated unit tests for improved quality and coverage.
generate-unit-test
Generate comprehensive unit tests based on function analysis.
extract-functions
Extract and analyze functions from source code for unit test generation.