gkw77

Rule Autopsy — Security skill for Claude Code

Security community

Audits a CLAUDE.md or rules folder and reports how many blocks claim an effect without a reproducible receipt, plus how many are covered by one.

How to install Rule Autopsy

This entry records only its repository, not the path inside it, so there is no exact command to give. Open gkw77/rule-autopsy and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Rule Autopsy does

Audits a CLAUDE.md or rules folder and reports how many blocks claim an effect without a reproducible receipt, plus how many are covered by one. Ships the dual audit scripts that produced the repository self-report.

Alternatives in Security

  • Mcp-scan (Invariant Labs) — MCP security scanner with proxy mode for real-time scanning without infrastructure changes 1.9k ★
  • Octoboss Clean Contexts — You are the Octoboss — a cross-tentacle orchestrator 1.4k ★
  • Openclaw Ops — OpenClaw operations skill with health checks, repair scripts, watchdogs, update triage, and security scans 225 ★

README

rule-autopsy

I maintain a rules system for agent work. One rule in it says: *a rule that isn't measured is faith, not fact.* So I ran that rule on the system itself.

**Result: of 50 rules that claim a measurable effect, 43 never measured it — 86%.**

The method re-runs on any rules directory in one command:

node verify-claims/verify-claims.js --self-corpus 

The 86% comes from a private corpus; only aggregate numbers are published. Two of the receipts that did measure something reproduce byte-for-byte in this repo (see `receipts/`). Read `docs/METHODOLOGY.md` before quoting any number.

The finding

The system is ~210 markdown blocks that tell agents to measure before they claim, to carry receipts, to treat unmeasured claims as faith. I scanned it with that same standard. Of **50 blocks that claim a measurable effect** ("cuts cost", "reduces false blocks", "intercepts X%"):

verdict count
measured — has a number and "we ran it" 7
cited from someone else — reproducible, not reproduced 7
claimed a number with no receipt at all 2
claimed an effect with no number to check 34
unproven, total 43 / 50 — 86%

The system is 78% prose by design; a rules system is supposed to be prose. The problem is narrower: of the blocks that promise an effect, 86% never prove it. And that is a floor — manual triage of the 7 "measured" flags shows at least 2 are the audit describing itself, not real measurements.

What reproduces

Two receipts run here today, offline and deterministically — their output matches the committed report line for line:

cd receipts/gzh-rig && python rig.py
# 19 seeded defects → double gate 19/19 (100%), best single gate 17/19 (89%), +2/19

cd receipts/agent-chief-rig && python scripts/readme_metrics.py
# 24 events → 96% intercepted, 75% reach LLM, 70% cache-hit, $0.104/1k

Three more receipts are documented with their exact limits (one needs a live model key