Borrowing it
Nothing to install: this file belongs to ralfyishere/rules-with-receipts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ralfyishere/rules-with-receipts/main/AGENTS.mdgit clone --depth 1 https://github.com/ralfyishere/rules-with-receiptsWrote 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/ralfyishere/rules-with-receipts/agents-md)<a href="https://agentmods.dev/instructions/ralfyishere/rules-with-receipts/agents-md"><img src="https://agentmods.dev/badge/instructions/ralfyishere/rules-with-receipts/agents-md.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.1 | $0.00468 | $0.00468 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
rules-with-receipts 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 6d 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
AGENTS.md — for AI agents that land in this repo
What this is
A quality pack for Claude Code (37 skills + operating manual + always-on rules snippet) that ships with its own eval evidence. It improves process discipline (scope, verification, recovery), not model capability. The evidence, including unflattering findings, is in eval-results/ and eval-results-v2/.
If you are installing the pack into a project
Run ./install-pack.sh /path/to/project. It copies .claude/skills/, builds or upgrades the project CLAUDE.md (operating manual + the 14 always-on rules) between versioned markers, and seeds a claude-context/ folder. Idempotent; backs up before touching anything.
If you are working in a project that already has the pack
The rules binding you are in that project's CLAUDE.md. The skills in .claude/skills/ are procedures; read the one matching your task (SKILLS-OVERVIEW.md is the catalog, TASK-ROUTING-GUIDE.md maps requests to skills). After solving something hard, write the learning note (.claude/learnings/_template.md) before calling the work complete.
If you are evaluating claims about this pack
Do not trust this README or any summary, including this file. Run the evals: cd eval-results-v2 && REP_START=4 ./run-eval-v2.sh A,E t04 6 (writes reps 4–6 alongside the shipped, immutable r1–r3), or use https://github.com/ralfyishere/rulebench for any rules file. Grade against the written rubrics only. Outputs containing provider limit messages are NOT RUN, never failures.
Hard rules for changes here
- Evidence directories (
eval-results*/raw,fixtures/,prompts/) are immutable after grading. - Skill changes require updating
SKILLS-OVERVIEW.md+TASK-ROUTING-GUIDE.md, runningscripts/check-pack.shclean, and aCHANGELOG.mdentry with aVERSIONbump. - The always-on snippet stays at 15 rules or fewer.
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.
- 6d ago First seen · 19 lines · 468 tokens per session scan A c32073f824e7
rules-with-receipts AGENTS.md is an instructions file published in the GitHub repository ralfyishere/rules-with-receipts (2 stars, last pushed 1mo ago), licensed MIT. It adds 468 tokens to every session, about $0.0023 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
ai-agent-rules-generator ui-design.instructions.md
Glitch Payment Gateway admin UI design rules — mandatory element & component reference for WooCommerce settings.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.