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 skills add ralfyishere/rules-with-receipts --skill correction-propagationgit 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/skills/ralfyishere/rules-with-receipts/correction-propagation)<a href="https://agentmods.dev/skills/ralfyishere/rules-with-receipts/correction-propagation"><img src="https://agentmods.dev/badge/skills/ralfyishere/rules-with-receipts/correction-propagation/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/skills/ralfyishere/rules-with-receipts/correction-propagation"><img src="https://agentmods.dev/badge/skills/ralfyishere/rules-with-receipts/correction-propagation.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.00139 | $0.01512 |
| Opus 5 | $0.00069 | $0.00756 |
| Sonnet 5 | $0.00028 | $0.00302 |
| Haiku 4.5 | $0.00014 | $0.00151 |
Grade A, and why
Correction Propagation 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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Correction Propagation
Purpose
The pack can MAKE claims (verification-discipline) and ATTACK them (adversarial-verify),
but nothing owns RETRACTING one after it has spread. A claim rarely lives in one place: the
same number, verdict, or headline gets restated in sibling docs, other repos, the public
mirror, READMEs, indexes, issue trackers, and memory files. When that claim is corrected —
downgraded, superseded, reversed, disproved — fixing the doc you happened to be looking at
leaves every other copy asserting the old, now-wrong version. Readers land on the stale one
and act on it.
This skill makes correction a sweep, not a spot-edit: name the claim's distinctive greppable tokens, enumerate every surface that could restate it, grep them all, banner or supersede each hit top-of-file first and dated, then re-grep to prove the sweep is clean. Only then is the correction done. It is the difference between "I fixed the README" and "the string '3/3' now appears in three repos, each bannered or deleted, re-grep returns only bannered hits."
When to use this skill
- You just corrected, retracted, downgraded, or reversed a claim you had published.
- A metric changed value, a status flipped (confirmed → disproved), or a conclusion reversed.
- A benchmark, number, or verdict you're fixing is restated somewhere else too.
- Someone asks "did the correction propagate?" or "is this still cited anywhere?"
- Closeout of any session where a correction happened.
- A claim that appears in more than one repo, doc, mirror, or memory file.
When NOT to use
- The claim never left one file and nothing restates it — a single edit is the whole job.
- You're making or grading a fresh claim, not changing one already out — that's
verification-discipline/empirical-validation. - The change is additive (new claim) and contradicts nothing previously published.
- Pure session-context staleness with no cross-artifact surfaces — that's
memory-hygiene.
The procedure
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.
- 9d ago First seen · 97 lines · 0 tokens per session scan A 8b99d056b1fa
Correction Propagation is a skill published in the GitHub repository ralfyishere/rules-with-receipts (2 stars, last pushed 2mo ago), licensed MIT. It adds 139 tokens to every session and 1,512 once invoked, about $0.0007 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 skills, from other repositories
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.
frontend-design
A design guide for building polished web interfaces such as pages, dashboards, forms, navigation, and reusable UI components. It covers HTML, CSS, JavaScript, and common frontend frameworks.
alterlab-cobrapy
Build and analyze genome-scale constraint-based metabolic models with COBRApy — flux balance analysis (FBA), flux variability analysis (FVA), gene and reaction knockouts, flux sampling, and SBML model I/O. Use when simulating metabolic networks, predicting growth or knockout phenotypes, or running systems-biology and…
alterlab-depmap
Query the Cancer Dependency Map (DepMap) for cancer cell line gene dependency scores (CRISPR Chronos), drug sensitivity data, and gene effect profiles. Use when identifying cancer-specific genetic vulnerabilities, finding synthetic lethal interactions, checking whether a gene is essential in given cell lines, or…
alterlab-qutip
Simulates open quantum systems with QuTiP, the Quantum Toolbox in Python, solving Lindblad master equations (mesolve), Monte Carlo trajectories (mcsolve), and unitary dynamics (sesolve). Use when studying master-equation or Lindblad dynamics, decoherence, dissipation, quantum optics, cavity QED, or open-system time…