stale-base-drops-rows-from-a-shared-ledger SKILL.md skillA
stale-base-drops-rows-from-a-shared-ledger 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/stale-base-drops-rows-from-a-shared-ledger@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/stale-base-drops-rows-from-a-shared-ledger/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Aug 11, 2026
- First version recorded
- Aug 10, 2026
- Size
- 13,879 bytes
- Repository stars
- 3
- License
- MIT
Trap: a branch that edits a SHARED HAND-EDITED LEDGER — one machine-parseable file every session appends rows to (a tracker `data.js`/`data.json`, a CHANGELOG, a registry, a manifest, a status board) — can DROP other sessions' rows on merge with **no file deletion and a perfectly ordinary diffstat**, so a file-level `--diff-filter=D` gate reports clean. This needs a stale **tree** (`git reset --soft`, or committing an old worktree with `git add -A`), not merely a stale branch point: a branch…
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 stale base drops rows from a shared ledger — no deletion, no conflict, ordinary diffstat ## Problem Your repo has one **hand-edited, machine-parseable ledger** that every session appends to: a progress tracker (`docs/site/assets/data.js`), a registry, a manifest, a CHANGELOG with structured entries. You branch, splice your rows in, and merge. Between your branch point and your merge, four other sessions appended THEIR rows to the same file. **If your branch's *tree* is stale — not merely its branch point — your commit genuinely records removing their rows, and git applies that faithfully with nothing to conflict against.** > ⚠️ **Be precise about the mechanism, because the loose version of it is false.** > Merely *being behind* `main` does not do this. Measured on a synthetic shared > ledger where two sessions append to the same file: > > | case | merge-tree | rows survive? | > |---|---|---| > | branch appends its own row from a stale base | **exit 1, CONFLICT** | — (loud) | > | branch regenerates the file from a stale copy | **exit 1, CONFLICT** | — (loud) | …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/stale-base-drops-rows-from-a-shared-ledger@sha256:4977335a8567c39cThe 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_ehrtkkp4ija3h4xg)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 10, 2026 and Aug 11, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-11 | f274e4b | 13,879 B | A | view · diff |
| v1.0.0 | 2026-08-10 | 319aa3b | 13,871 B | A | view |
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 (13879 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_ehrtkkp4ija3h4xg GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/stale-base-drops-rows-from-a-shared-ledger GET https://markdownregistry.com/api/v1/blob/4977335a8567c39cc070f6d7ace1a3f618187e0e3975a0f2c7741cc58b52214c
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.