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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/ralfyishere/rules-with-receipts/claude-md"><img src="https://agentmods.dev/badge/instructions/ralfyishere/rules-with-receipts/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/ralfyishere/rules-with-receipts/claude-md"><img src="https://agentmods.dev/badge/instructions/ralfyishere/rules-with-receipts/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01353 | $0.01353 |
| Opus 5 | $0.00677 | $0.00677 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
rules-with-receipts CLAUDE.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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fable Skills — pack source repository
This directory IS the quality pack's source. Sessions here are usually maintaining the pack. Maintainer rules:
- Evidence is immutable: never edit anything under
eval-results*/raw/,fixtures/, orprompts/after a run has been graded. New experiments get new files. - Indexes stay in sync: after adding/renaming/removing a skill, update
SKILLS-OVERVIEW.mdandTASK-ROUTING-GUIDE.mdin the same change, then runscripts/check-pack.sh— it must exit clean before committing. - Regression before release: after any substantive skill/snippet/manual change, run the regression pair —
cd eval-results-v2 && ./run-eval-v2.sh all t02,t04 3— and grep outputs for "hit your session limit" stubs before grading (quota stubs = NOT RUN, never FAIL). - Releases follow
RELEASE-CHECKLIST.md:scripts/make-release-bundle.shenforces every AUTO item and refuses to bundle otherwise; the three MANUAL items get attested in the release notes. - Version on change: bump
VERSION+ add aCHANGELOG.mdentry for any change to skills, snippet, manual, or installer. Installed projects upgrade via re-runninginstall-pack.sh. - Snippet stays ≤ ~15 rules; this file stays lean — procedures belong in skills, not here.
- Changing a proven component requires an A/B, not just a count check. Before adding to / rewording the snippet, an exemplar, or anything with measured effect, run a controlled experiment (isolate the one change,
eval-results-v2/ab-snippet-t04.shis the template) — attention budget is scarce and a "good" addition can dilute the proven effect (learned the hard way: the session-orientation snippet rule cut t04 flagging ~9/12 → ~1/9). A new skill can ship as a skill without also claiming an always-on slot. - Skill-triggering can only be tested in fresh
claude -psessions in temp dirs outside this tree — never via subagents (they inherit the parent's skill snapshot). - Continuity layer:
ACTIVE-PROJECTS.md(state registry) +SESSION-START.md(orientation procedure) are private, never mirrored. Read the registry at session start; update the touched entries at closeout of any session that changes project state. Durable work never stays in session scratchpads. - Final closeout before any completion claim: after any pack/publish/mirror change, run
scripts/closeout-check.sh(plus, for mirror work, with the public-clone path) AND do a manual behavior-claims review of docs the script can't judge. "Everything is done" is forbidden unless that sweep passed; claims in the final response are limited to what was actually checked, and anything unchecked is named as unchecked. Local verification is not global completion.
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.
- 8d ago First seen · 61 lines · 1,353 tokens per session scan A 0073aea77200
rules-with-receipts CLAUDE.md is an instructions file published in the GitHub repository ralfyishere/rules-with-receipts (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,353 tokens to every session, about $0.0068 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.