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/futureexcited/vibe-rules/examplesgit clone --depth 1 https://github.com/FutureExcited/vibe-rulesWhat 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.00000 | $0.00051 |
| Opus 5 | $0.00000 | $0.00026 |
| Sonnet 5 | $0.00000 | $0.00010 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
examples 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 yesterday.
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
When working in the examples directory you have to run bun run build and bun build:examples to build any code changes to js files before you can test them.
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.
- yesterday First seen · 7 lines · 0 tokens per session scan A 7618119f3f3c
examples is a cursor rule published in the GitHub repository FutureExcited/vibe-rules (529 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 51 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-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.