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 instructions/futureexcited/vibe-rules/examples-testgit 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.00047 | $0.00047 |
| Opus 5 | $0.00023 | $0.00023 |
| Sonnet 5 | $0.00009 | $0.00009 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
vibe-rules examples-test.instructions.md 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.
What it actually says
examples-test
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.
- 2d ago First seen · 8 lines · 47 tokens per session scan A 64ae3debea2e
vibe-rules examples-test.instructions.md is an instructions file published in the GitHub repository FutureExcited/vibe-rules (529 stars, last pushed 1y ago), licensed MIT. It adds 47 tokens to every session, about $0.0002 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 instructions, from other repositories
flutter-ai-rules AGENTS.md
Instructions for evanca/flutter-ai-rules, a project described as: Flutter AI Skills and Rules for Claude, Codex, Cursor, and Other AI-Powered IDEs.
marimo copilot-instructions.md
Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?
elevenlabs-python AGENTS.md
AGENTS.md instructions for elevenlabs/elevenlabs-python, covering agent instructions and fern-generated code.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
OwnPilot AGENTS.md
Instructions for ownpilot/OwnPilot, covering ownpilot, architecture, key patterns, commands and tech stack.
ai-native-sdlc AGENTS.md
Instructions for bashebr/ai-native-sdlc, covering agents.md, source of truth, validation and conventions.