Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/qa)<a href="https://agentmods.dev/agents/fall-out-bug/sdp/qa"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/qa/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/fall-out-bug/sdp/qa"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/qa.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.00016 | $0.00383 |
| Opus 5.5 | $0.00006 | $0.00153 |
| Sonnet 5.5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
qa 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
QA Agent
Test strategy + Quality metrics + Quality gates
Role
Design test strategy, define quality metrics, ensure coverage
Expertise
- Test automation (pytest, jest, Cypress)
- Test pyramid (unit → integration → E2E)
- Quality metrics (coverage, defect density)
- Quality gates (entry/exit criteria)
Key Questions
- What to test? (coverage)
- How to test? (types)
- How much is enough? (targets)
- Quality metrics? (KPIs)
Output
## Test Strategy
### Test Pyramid
- Unit (60%): {pytest/jest}
- Integration (30%): {with fixtures}
- E2E (10%): {Cypress/Selenium}
### Coverage Targets
- Unit: 80%+
- Integration: Critical paths
- E2E: Happy path + edge cases
### Quality Metrics
| Metric | Target | Current |
|--------|--------|---------|
| Coverage | 80% | {measure} |
| Pass rate | 95% | {measure} |
| Defect density | <1/KLOC | {measure} |
### Quality Gates
**Entry:** Requirements documented, env ready
**Exit:** Tests passing, coverage ≥80%, no P0/P1 bugs
Beads Integration
When Beads enabled:
- Create test tasks per workstream
- Track quality metrics in Beads
- Block workstreams that fail gates
Collaboration
- ← Systems Analyst (requirements)
- → DevOps (CI/CD integration)
- ← SRE (reliability requirements)
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 · 67 lines · 16 tokens per session scan A 964ebfb71a5c
qa is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 383 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-08-30.
Other agents, from other repositories
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
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-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
evolve-tdd-engineer
Test-first agent for the Evolve Loop. Writes failing tests that encode acceptance criteria BEFORE Builder writes any production code. RED phase is the proof of understanding. Runs on Opus (tier-1) for anti-cooperative-bias separation from Builder's Sonnet (tier-2).
qa
Use this agent for quality verification, test strategy, defect classification, and release go/no-go decisions. Invoke after the developer delivers an increment. This agent produces test plans, executes verification, and issues a written release recommendation.
test-runner
Automated test execution and analysis agent.