the Method

Everything the index claims comes from one kind of evidence: a repo's own git history. Nothing here asks a model for an opinion.

What counts as a rule

A structured line in an agent instruction file: a key: value pair or a - term — definition bullet. Free-prose instructions are not tracked — the detector does not guess at prose.

Which files

The files agents read as law: CLAUDE.md, AGENTS.md, .cursorrules, and friends. The scanner prints exactly what it scanned, every run.

What a zombie is, precisely

A rule removed in one commit and re-added in a later one — located by diffing consecutive versions of the file. The bytes decide. Each finding cites both commits. Mass file-swaps (a merge oscillating between two versions) are collapsed to a single churn event rather than counted as many zombies; a rule that returns with different wording is flagged for human review, never auto-judged.

The score

A 0–100 belief-integrity number computed under a frozen, hash-committed formula: active zombies dominate and saturate; historical revivals add a small memory penalty; retraction hygiene can only reduce penalties, never add points. The weights were committed before any repo was scored and cannot be quietly retuned — changes require a new version with a public changelog.

method sha256:f747fe9f1f6f2814aacfff1f98597f8b2c325e00e6ddcae99c6b7ad95f860aae

What is not measured

Whether your agent answers correctly. Code quality. Security. Anything a model said. A score of 100 means "no zombie beliefs detectable among structured rules" — nothing more.

Recompute the verdict

Every number on this site traces to a signed receipt you can verify in this browser, offline in two independent languages, or by rerunning the scan against the repo's own public history: uvx sagrada-linter scan-history . If you get a different answer than we did, that is a finding — tell us.