parallel-impl-agent-dies-mid-stream-verify-working-tree SKILL.md skillA
parallel-impl-agent-dies-mid-stream-verify-working-tree 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/parallel-impl-agent-dies-mid-stream-verify-working-tree@v1.3.0Pins v1.3.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/parallel-impl-agent-dies-mid-stream-verify-working-tree/SKILL.md- Versions recorded
- 5
- Latest version
- v1.3.0, committed Sep 12, 2026
- First version recorded
- Jul 8, 2026
- Size
- 10,058 bytes
- Repository stars
- 3
- License
- MIT
A dispatched parallel implementation subagent can die mid-stream and leave ZERO durable output while the harness still reports the task "completed". Use when: (1) you fanned out 2+ foreground impl agents (Agent/Task tool) to edit code in one repo, (2) one returns `API Error: Response stalled mid-stream` / an empty or truncated final message, possibly alongside a background "<task> completed (exit code 0)" notification, (3) you're about to integrate or commit their combined work. The…
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
# Parallel impl agent dies mid-stream — verify the working tree, not "completed" ## Problem You dispatch N foreground implementation agents in parallel (disjoint files). One comes back with `API Error: Response stalled mid-stream` (or an empty/truncated report), and the harness may even emit a background "<task> completed (exit code 0)" line. If you trust that and integrate, you ship a hole: the agent wrote NOTHING — its target route is untouched, no test file exists, the todos it created for itself are all still `pending`. ## Context / Trigger Conditions - 2+ parallel `Agent`/`Task` impl agents editing code in one repo. - One returns a stall/timeout/empty final message; `subagent_tokens` ~0; a "completed" status. - You're about to run a combined `git add`/commit or a whole-repo check across both outputs. ## Solution 1. **Reconcile claimed-vs-actual before integrating.** For each agent: `git status --short` and grep its target for the expected change (e.g. `grep -n buildResponse handler.ts`). A missing edit + no new test file = the agent died; "completed (exit 0)" was the harness reporting the shell wrapper exited, NOT the work landing. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/parallel-impl-agent-dies-mid-stream-verify-working-tree@sha256:6f8227a1f7c59de0The line at the top of this page pins the label v1.3.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_6zvgzb2vhuj6vmyt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 8, 2026 and Sep 12, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.3.0 latest | 2026-09-12 | aec1aa9 | 10,058 B | A | view · diff |
| v1.3.0 | 2026-08-11 | f274e4b | 10,665 B | A | view · diff |
| v1.3.0 | 2026-07-23 | b530a0f | 10,653 B | A | view · diff |
| v1.2.0 | 2026-07-23 | fe5305e | 9,462 B | A | view · diff |
| v1.0.0 | 2026-07-08 | 7f737d2 | 4,108 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 (10058 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_6zvgzb2vhuj6vmyt GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/parallel-impl-agent-dies-mid-stream-verify-working-tree GET https://markdownregistry.com/api/v1/blob/6f8227a1f7c59de06086b394647e33409c403095c60a7687123177c366fc3172
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.