subagent-pre-existing-misattribution SKILL.md skillA
subagent-pre-existing-misattribution 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/subagent-pre-existing-misattribution@v1.1.2Pins v1.1.2 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/subagent-pre-existing-misattribution/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.2, committed Aug 12, 2026
- First version recorded
- May 13, 2026
- Size
- 11,360 bytes
- Repository stars
- 3
- License
- MIT
Catch subagent reviewers misattributing test failures across the pre-existing / PR-introduced boundary — in BOTH directions. Use when: (1) a multi-task subagent-driven plan reports "N pre-existing failures, unrelated" across consecutive tasks and the count never changes, (2) an architectural / final reviewer at the end catches assertions that should have been updated 5 tasks ago, (3) an implementer reports "verified pre-existing on clean tree by running git stash" but the breaking change…
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
# Subagent-Driven Development: Pre-Existing Failure Misattribution ## Problem In subagent-driven development, each task's reviewer evaluates spec compliance + code quality for THAT task in isolation. When the implementer or reviewer runs the full suite and finds N failures, they look up whether those failures are "new from this task" or "pre-existing baseline." If they classify them wrong, the failures get carried forward as "known unrelated failures" through every subsequent task — and the final architectural reviewer is the only checkpoint that catches the misattribution. The specific failure mode: an early task removes an item from a list (e.g., a sidebar nav entry, a collection of dashboard cards). Other test files have HARDCODED COUNT ASSERTIONS for that list (`assert count == 5`) that nobody notices because: 1. The implementer of the breaking task fixes the parametrize lists they SEE but misses count assertions in OTHER test files. 2. The implementer reports "8 failures, all pre-existing — verified on clean tree." 3. Subsequent task implementers/reviewers see "baseline = 8 failures" and treat anything matching that count as expected. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/subagent-pre-existing-misattribution@sha256:3b9fa4bfda045bedThe line at the top of this page pins the label v1.1.2, 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_5ae2gdxoiu5m6bsr)
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.2 latest | 2026-08-12 | 58306d9 | 11,360 B | A | view · diff |
| v1.1.1 | 2026-08-10 | ff2caaa | 11,428 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 11,108 B | A | view · diff |
| v1.1.0 | 2026-05-29 | 059688a | 11,077 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 8,962 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 (11360 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_5ae2gdxoiu5m6bsr GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/subagent-pre-existing-misattribution GET https://markdownregistry.com/api/v1/blob/3b9fa4bfda045bedd05c2a81efed5377433c854aa213bf0a1af3275cde4f1ebb
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.