rule-cited-by-title-proposes-work-the-ledger-says-is-built SKILL.md skillA
rule-cited-by-title-proposes-work-the-ledger-says-is-built from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/rule-cited-by-title-proposes-work-the-ledger-says-is-built@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/rule-cited-by-title-proposes-work-the-ledger-says-is-built/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 17, 2026
- Size
- 12,930 bytes
- Repository stars
- 3
- License
- MIT
A standing rule ("no change to X until the owner has reviewed Y") cited from its TITLE, its id, or a peer's paraphrase instead of its recorded body — so a session proposes building Y when the shared ledger already carries Y as built and waiting on a human. The second half is a vocabulary trap: a status word that means "built, unreviewed" is usually spelled `open` or `pending`, which in issue vocabulary means "not started", so the row that proves the work exists reads as proof it does not. Use…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# A rule cited by title proposes work the ledger says is already built
## Problem
A repo keeps its standing decisions and its deliverables in one **hand-edited,
machine-parseable ledger** — a tracker `data.js`, a registry, a manifest, a decisions
table. Decisions have ids. Artifacts have rows with a `status`. Both are read by every
session, which is the point of keeping them there.
A session reads a rule by its **id**:
```
d-the-threshold-is-charted-before-it-moves
```
That id is a complete sentence and it sounds like the whole rule. The session concludes:
any change to the threshold needs a chart of the outputs at each candidate value, and
nobody has charted them — so it writes the owner an option card offering to build exactly
that.
Two things were never read.
**The rule's own body**, which said the charts are required *and already commissioned*:
```
"ruling": "A change to the threshold ships with the outputs charted at each candidate
value, reviewed by me before the value moves. Commissioned 2026-08-30."
```
**The artifact rows**, which carried the deliverable twice:
```json
…Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/rule-cited-by-title-proposes-work-the-ledger-says-is-built@sha256:269de413c22ee63dThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pcmgueg5q6k4uydv)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 17, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12930 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pcmgueg5q6k4uydv GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/rule-cited-by-title-proposes-work-the-ledger-says-is-built GET https://markdownregistry.com/api/v1/blob/269de413c22ee63db1ecfe060849d392d4dc79f03ebd3fe063eaec56b765c39c
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.