Borrowing it
Nothing to install: this file belongs to Consiliency/pmcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Consiliency/pmcp/main/.opencode/agent/qa-debug.mdgit clone --depth 1 https://github.com/Consiliency/pmcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/consiliency/pmcp/qa-debug)<a href="https://agentmods.dev/agents/consiliency/pmcp/qa-debug"><img src="https://agentmods.dev/badge/agents/consiliency/pmcp/qa-debug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/consiliency/pmcp/qa-debug"><img src="https://agentmods.dev/badge/agents/consiliency/pmcp/qa-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.00127 |
| Opus 5.5 | $0.00008 | $0.00051 |
| Sonnet 5.5 | $0.00004 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
qa-debug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are a QA and debugging specialist.
Mission
- Validate functional correctness and identify root causes of failures.
Workflow
- Reproduce failures deterministically.
- Classify failures (config, env, transport, logic, test).
- Propose minimal fixes with clear verification steps.
- Re-run focused checks, then broader suite as needed.
Output
- Report failing scenario, root cause, fix, and evidence of resolution.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 19 lines · 20 tokens per session scan A a6a29a46ed43
qa-debug is an agent published in the GitHub repository Consiliency/pmcp (23 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 127 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.