credit-stall-mid-orchestration-revive-collision SKILL.md skillA
credit-stall-mid-orchestration-revive-collision 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/credit-stall-mid-orchestration-revive-collision@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/credit-stall-mid-orchestration-revive-collision/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.0, committed Aug 12, 2026
- First version recorded
- May 13, 2026
- Size
- 13,855 bytes
- Repository stars
- 3
- License
- MIT
Recover gracefully when an Anthropic credit/billing failure stalls multiple in-flight parallel subagents mid-orchestration, then later resolves. Use when: (1) you've dispatched 2+ parallel subagents (Task tool with `run_in_background: true`) and a credit/billing issue, MCP outage, or other transient harness failure has frozen them, (2) the user reports the issue is now resolved and asks you to continue, (3) you're about to relaunch "resume" agents to pick up where stalled originals left…
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
# Credit-stall mid-orchestration: revive-collision recovery ## Problem You're orchestrating N parallel subagents (Task tool with `run_in_background: true`), each working on independent tracks (e.g., one PR per track). Mid-run, an Anthropic billing/credit failure or other transient harness outage hits — all in-flight subagents freeze simultaneously. The user fixes billing, reports back, and asks you to continue. **The trap:** stalled subagents are NOT dead — they're suspended at the harness layer. When API access is restored, the harness can auto-resume them from the exact tool-call boundary they froze on. If you naively relaunch "resume" agents to pick up where you think the originals stopped, you end up with TWO agents racing on: - The same git branch (one commits + pushes, the other rebases on top of stale state) - The same PR (duplicate review comments, conflicting label changes) - The same files (one Edit lands, then the other Edit overwrites) Symptoms when this happens: PR has two "no issues found" review comments, force-push storms as both agents rebase, agent A reports "PR already merged" while agent B is still polling CI for that same PR. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/credit-stall-mid-orchestration-revive-collision@sha256:99501005fecfe8a6The 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_wiu7sjxpn5y2xpv2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 13, 2026 and Aug 12, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-12 | 9a8e5a8 | 13,855 B | A | view · diff |
| v1.1.0 | 2026-08-12 | f461c97 | 13,843 B | A | view · diff |
| v1.1.0 | 2026-08-05 | e3930cf | 13,724 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 13,877 B | A | view · diff |
| v1.1.0 | 2026-05-13 | 07472bf | 13,866 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 (13855 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_wiu7sjxpn5y2xpv2 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/credit-stall-mid-orchestration-revive-collision GET https://markdownregistry.com/api/v1/blob/99501005fecfe8a614a2bec7e0cf82c008fe229103f971dc5faca7d9392f33d3
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.