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/13624725933/agent-rulescope/testsgit clone --depth 1 https://github.com/13624725933/agent-rulescopeWrote 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/instructions/13624725933/agent-rulescope/tests)<a href="https://agentmods.dev/instructions/13624725933/agent-rulescope/tests"><img src="https://agentmods.dev/badge/instructions/13624725933/agent-rulescope/tests.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 | $0.00038 | $0.00038 |
| Opus 5 | $0.00019 | $0.00019 |
| Sonnet 5 | $0.00008 | $0.00008 |
| Haiku 4.5 | $0.00004 | $0.00004 |
Grade A, and why
agent-rulescope tests.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 3d 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
- Use descriptive test names that state the observable behavior.
- Keep test fixtures local to the test that owns 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.
- 3d ago First seen · 7 lines · 38 tokens per session scan A 3da0391332b7
agent-rulescope tests.instructions.md is an instructions file published in the GitHub repository 13624725933/agent-rulescope (1 stars, last pushed 1mo ago), licensed MIT. It adds 38 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-31.
Other instructions, from other repositories
x-harness AGENTS.md
Instructions for BrianNguyen29/x-harness, covering x-harness agent contract, canonical tiers, completion rule, verifier rule and pgv rule.
cursor-os AGENTS.md
Instructions for KingEmma7/cursor-os, covering agents.md — cursor-os, what this project is, repository layout, working agreements and verification before done.
agent-context-doctor copilot-instructions.md
Copilot instructions for lamguo/agent-context-doctor, covering github copilot instructions, agents.md, project overview, setup commands and development commands.
agent-context-doctor CLAUDE.md
Claude Code instructions for lamguo/agent-context-doctor, covering claude.md, agents.md, project overview, setup commands and development commands.
ctxlint copilot-instructions.md
Copilot instructions for tqakdev/ctxlint, covering copilot instructions — acme-orders, workflow, components and style.
agents-md-templates AGENTS.md
Instructions for abhishekray07/agents-md-templates, covering agents.md, project, structure, conventions and don't.