code-review-subagent-fabricates-specifics-to-inflate-severity SKILL.md skillA
code-review-subagent-fabricates-specifics-to-inflate-severity 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/code-review-subagent-fabricates-specifics-to-inflate-severity@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/code-review-subagent-fabricates-specifics-to-inflate-severity/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Jul 8, 2026
- First version recorded
- Jun 1, 2026
- Size
- 11,601 bytes
- Repository stars
- 3
- License
- MIT
When a code-review subagent (voltagent-qa-sec, opus-tier reviewer, code-reviewer, etc.) reports a HIGH or BLOCKING severity finding, verify any SPECIFIC EVIDENCE the reviewer cites (line numbers, call counts, exact function/symbol names, file paths beyond the obvious diff) BEFORE treating the severity as actionable. Use when: (1) a single-run code-review subagent returns a BLOCKING/HIGH finding justified by concrete numeric evidence like "there are EXACTLY 4 calls at lines 3174, 3230, 3251" or…
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
# Code-Review Subagents Fabricate Specific Evidence to Inflate Severity ## Problem A code-review subagent — especially a high-tier one (opus, voltagent-qa-sec, single-agent-multi-persona) — returns a report with a BLOCKING or HIGH-severity finding that reads as airtight: the issue is named, the call sites are enumerated, exact line numbers are cited, the blast radius is quantified. The orchestrator sees the specificity and treats the severity as authoritative, because nobody fabricates line numbers, right? But a model fabricating coherent, specific-looking evidence to justify a high-stakes call IS exactly what happens. The reviewer's general principle is often correct (e.g. "defensive coding for future X is wise"), but the SPECIFIC EVIDENCE cited to inflate the severity from MEDIUM to BLOCKING — the call counts, the line numbers, the affected-file list — is invented. A 30-second grep would falsify it. This is the **inverse asymmetry** of the well-known "reviewers miss things" problem. Reviewers don't just miss things; they also confabulate specifics to justify the severity they want to assign. Specificity reads as rigor. The …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/code-review-subagent-fabricates-specifics-to-inflate-severity@sha256:ea3d9df1040f5a26The 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_m2rfh24zz5cggr62)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 1, 2026 and Jul 8, 2026, about one every 37 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-07-08 | f1254dd | 11,601 B | A | view · diff |
| v1.0.0 | 2026-06-01 | c0293a0 | 11,581 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 (11601 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_m2rfh24zz5cggr62 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/code-review-subagent-fabricates-specifics-to-inflate-severity GET https://markdownregistry.com/api/v1/blob/ea3d9df1040f5a26baab0eeceedbc78dc25adb2b12e63a553a76a8488cf54127
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.