bug-provenance skillC
bug-provenance is agent-read markdown (skill) from clickety-clacks/tightbeam.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Bug provenance
A causal investigation behind one bug, ending in a classified verdict and a routed fix
plan. This is not recon's mapping ("what is here") — it is the autopsy ("why is this so").
You diagnose; you never operate: **this skill forbids editing implementation files.** A
diagnosis loses its independence the moment the diagnostician starts fixing.
1. Classify the bug into exactly one cause class, and route it:
| Class | Meaning | Route |
|---|---|---|
| `code-violates-spec` | spec right, code wrong | fix plan for the code; dispatch implementation |
| `spec-hole` | the behavior is undefined | file the hole for a spec ruling FIRST; the fix is blocked until the owning spec gains the ratified sentence |
| `stale-spec` | spec contradicts ratified intent | spec amendment first, then code — never obey a stale spec into destroying working behavior |
| `spec-conflict` | two specs disagree at a seam | adjudication first; no code until authority is ruled |
| `wrong-proof` | code right, spec right, the test asserts an old implementation's accident as intent | fix the oracle AND audit what it masked while wrong |
…Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/bug-provenance@git:20260809.1917466mdr add clickety-clacks/tightbeam/bug-provenance@sha256:6deaf672374792c6Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_5u2v27icip735xmg)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260809.1917466 latest | 2026-08-09 | 1917466 | 2,699 B | C | view · diff |
| git:20260723.838baaa | 2026-07-23 | 838baaa | 2,511 B | C | view |
Audit of the latest version
- fail: Frontmatter block present
- fail: Frontmatter declares a name
- fail: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2699 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
clickety-clacks/tightbeam · 14 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5u2v27icip735xmg GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/bug-provenance GET https://markdownregistry.com/api/v1/blob/6deaf672374792c66773c802db1038b8a6ee9f239a0aa20fd232d190cfaae2e6
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.