verify-live-prod-before-shipping-superseded-fix SKILL.md skillA
verify-live-prod-before-shipping-superseded-fix 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/verify-live-prod-before-shipping-superseded-fix@v1.1.0Pins v1.1.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/verify-live-prod-before-shipping-superseded-fix/SKILL.md- Versions recorded
- 2
- Latest version
- v1.1.0, committed Sep 12, 2026
- First version recorded
- Aug 12, 2026
- Size
- 8,625 bytes
- Repository stars
- 3
- License
- MIT
A parallel Claude/work session shipped a DIFFERENT (often better) fix to the SAME live-prod artifact for the SAME issue while you were mid-build — so your fully-implemented, validated, reviewed fix is now REDUNDANT and must NOT be deployed over theirs. Use when: (1) you picked up a "next session ships the scoped fix X" handoff/prompt and invested a full implementation, (2) the target is a SHARED prod artifact (Dataform .sqlx, a serving feature table, a deploy config, a model pointer) editable…
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 parallel session superseded your validated fix — verify LIVE prod state before building/deploying ## Problem You took a "next session ships the scoped fix" handoff, did everything right — diagnosed, designed, panel-reviewed, implemented, validated end-to-end — and then discovered a **parallel session already shipped a DIFFERENT fix for the SAME issue to the SAME live-prod artifact**, mid-flight. Your work is redundant, and worse: deploying it would **clobber the live fix** (two mechanisms on one file). The handoff was accurate when written but the world moved. ## Context / Trigger Conditions - A multi-session / multi-worktree repo where >1 session can edit the same prod artifact. - A handoff or prompt that says "NEXT SESSION ships fix X" (X already scoped) — you executed it faithfully. - Target is a **shared prod artifact**: a Dataform `.sqlx` on the deployed branch, a serving feature table, a Cloud Run/deploy config, a `latest_good_model` pointer. - The driving issue is **still OPEN**, but a **sibling issue CLOSED** unexpectedly (the early signal). - You're about to deploy and your last look at the live artifact was at task start (stale). …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/verify-live-prod-before-shipping-superseded-fix@sha256:0004bada79cb2465The line at the top of this page pins the label v1.1.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_ld5t7ysxq56daihz)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 12, 2026 and Sep 12, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-09-12 | aec1aa9 | 8,625 B | A | view · diff |
| v1.1.0 | 2026-08-12 | 5811428 | 9,327 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 (8625 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_ld5t7ysxq56daihz GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/verify-live-prod-before-shipping-superseded-fix GET https://markdownregistry.com/api/v1/blob/0004bada79cb2465226750605d984ac40637315be7b6a814d40742b381175a87
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.