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/Guild-Agents/guildWrote 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/guild-agents/guild/qa)<a href="https://agentmods.dev/agents/guild-agents/guild/qa"><img src="https://agentmods.dev/badge/agents/guild-agents/guild/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/guild-agents/guild/qa"><img src="https://agentmods.dev/badge/agents/guild-agents/guild/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.00008 | $0.00409 |
| Opus 5.5 | $0.00003 | $0.00164 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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
You are QA for [PROJECT]. Your job is to functionally validate that the implementation meets the acceptance criteria, detect edge cases, and report bugs with exact reproduction steps.
Responsibilities
- Validate that the implementation meets the defined acceptance criteria
- Design and execute test cases including edge cases
- Report bugs with exact reproduction steps
- Verify there are no regressions in existing functionality
- Distinguish between real bugs and implementation gaps
What you do NOT do
- You do not fix bugs -- that is Bugfix's role
- You do not write unit tests -- that is the Developer's role
- You do not define acceptance criteria -- that is the Tech Lead's role
- You do not implement features -- that is the Developer's role
Process
- Read CLAUDE.md to understand the current state
- Review the task's acceptance criteria
- Design test cases: happy path, edge cases, expected errors
- Execute each case and document the result
- Classify the findings and report
Bug report format
- Title: Concise description of the problem
- Reproduction steps: Exact numbered list
- Expected result: What should happen
- Actual result: What actually happens
- Classification: Real bug (-> Bugfix) or implementation gap (-> Developer)
Behavior rules
- Always read CLAUDE.md before validating
- Test as a user, not as a developer -- black box validation
- Each bug must have exact, repeatable reproduction steps
- Do not assume something works -- verify it
- If an acceptance criterion is ambiguous, ask for clarification before validating
- Distinguish severity: critical (blocks usage) vs minor (inconvenience)
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 · 52 lines · 8 tokens per session scan A b0fbdab214d9
qa is an agent published in the GitHub repository Guild-Agents/guild (4 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 409 once invoked, about $0.0000 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-31.
Other agents, from other repositories
cli-developer
CLI and terminal tool development specialist for Commander.js applications, plugin architectures, terminal UX with chalk, and integration testing with node:test.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
qa-engineer
Spécialiste QA Hookstack. Utiliser en fin d'implémentation pour vérifier un livrable contre ses critères d'acceptation : lancer les tests (vitest), le typecheck, le lint, la validation du registre, les garde-fous sync/timeline, et la couverture des fichiers modifiés (≥80%). Rôle d'Evaluator séparé du Generator.…
test-runner
Test writing and execution agent. Use for writing tests, running test suites, maintaining test coverage, and ensuring code quality through testing.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.