executed-prompt-not-retired-sibling-redoes-it SKILL.md skillA
executed-prompt-not-retired-sibling-redoes-it 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/executed-prompt-not-retired-sibling-redoes-it@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/executed-prompt-not-retired-sibling-redoes-it/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Aug 5, 2026
- Size
- 9,277 bytes
- Repository stars
- 3
- License
- MIT
A prompt/brief/runbook file and the index that lists it are SHARED STATE between parallel sessions, so finishing the work is only half of finishing: the session that executes a brief must retire it on BOTH surfaces, and the session that writes one must register it, or a sibling redoes work that already merged or never sees the file at all. Use when: (1) you are about to execute a brief from a handoffs/plans/runbooks directory, or an index says "take this one" / "next" / "live, unclaimed"; (2)…
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
# An executed prompt nobody retired: the next session redoes merged work ## Problem A repo keeps session briefs in `docs/handoffs/` with an index, `next_session_prompt.md`, whose table says which are live. Sessions run in parallel and pick their work off that table. Session A executes `2026-08-05-registered-scope-drift.md` in full: the analysis lands, a ruling is committed, the issue is closed, the PR merges. Session A writes an excellent handoff about what it found. **It does not touch the brief it executed, or the row that pointed at it.** An hour later the index still reads: > `| 2026-08-05-registered-scope-drift.md | ... | live, unclaimed — **TAKE THIS ONE** |` and the brief itself still opens *"Nothing here is blocked and nothing needs the owner to start."* A fresh session, told only "read the index and take the top row", starts re-deriving a result that merged an hour ago. The same repo hit the identical shape twice in one day: a second stream's brief said "task 1: classify the marks", the marks had been classified that morning, and the PR that caught it is titled *"the prompt would have commissioned a rival tally against the committed one"* — the …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/executed-prompt-not-retired-sibling-redoes-it@sha256:5838098dcd110ca6The 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_cp76dpcsdtjsc2ll)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 5, 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 (9277 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_cp76dpcsdtjsc2ll GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/executed-prompt-not-retired-sibling-redoes-it GET https://markdownregistry.com/api/v1/blob/5838098dcd110ca68d76ac9a7997db04f3ca4bc60691a2b3c178f0abb9778cac
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.