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/z35068037/whichrules/agents-mdgit clone --depth 1 https://github.com/z35068037/whichrulesWhat 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.00076 | $0.00076 |
| Opus 5 | $0.00038 | $0.00038 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
whichrules AGENTS.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
WhichRules contributor instructions
- Use Node.js 20 or newer and npm for local scripts.
- Run
npm run checkbefore submitting changes. - Keep the CLI zero-runtime-dependency and offline by default.
- Add a fixture and a test for every new instruction format or rule detector.
- Do not weaken conflict evidence: every finding must include a file and line.
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 · 76 tokens per session scan A 195963bcf30b
whichrules AGENTS.md is an instructions file published in the GitHub repository z35068037/whichrules (4 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session, about $0.0004 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-31.
Other instructions, from other repositories
vibe-check AGENTS.md
Instructions for benavlabs/vibe-check, covering security rules, secrets, database, authentication and authorization and input and output.
conforme AGENTS.md
Instructions for maxgfr/conforme, covering project instructions, claude.md, project overview, build & test and architecture.
conforme GEMINI.md
Instructions for maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
ai-agent-instruction-modules AGENTS.md
Instructions for tablackburn/ai-agent-instruction-modules, covering ai agent instructions, instructions for ai agents, instruction applicability matrix, available instruction files and quick reference.
conforme copilot-instructions.md
Instructions for maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
conforme adapter-consistency.instructions.md
Instructions for maxgfr/conforme, a project described as: Sync your AI coding config from Claude Code, Cursor, or any tool — rules, skills, agents, MCP servers.