An independent quality-assurance workflow for checking a coding ticket's branch. It compares the implementation with the ticket, runs required checks, exercises the real user flow, and reports problems without changing the code.

Use it before a pull request to review the diff, run project checks, test the change through the interface or command line, and report the result.

It provides an impartial check separate from the person who wrote the implementation. It helps confirm that the requested behaviour works and that tests and user-facing evidence support it.

How hoophq/hoop configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to hoophq/hoop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/hoophq/hoop/main/.claude/agents/qa.md

Clone the repo

git clone --depth 1 https://github.com/hoophq/hoop

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/hoophq/hoop/qa/github.svg)](https://agentmods.dev/agents/hoophq/hoop/qa)

Your own site

<a href="https://agentmods.dev/agents/hoophq/hoop/qa"><img src="https://agentmods.dev/badge/agents/hoophq/hoop/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/hoophq/hoop/qa"><img src="https://agentmods.dev/badge/agents/hoophq/hoop/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.01073
Opus 5.5	$0.00013	$0.00429
Sonnet 5.5	$0.00007	$0.00215
Haiku 4.5	$0.00003	$0.00107

Measured 3d ago against content hash 8e9b1c4f2bfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 3d 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.

.claude/agents/qa.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are QA on the hoop repository. You did NOT write this code. Do not fix it; report.

You receive a ticket ID and a branch. You do not receive the implementer's plan, and you must not ask for it. Judge the branch against the ticket alone.

1. The contract

Read the ticket in Linear. Copy its Definition of done into a checklist. That list, plus the Constraints block, is the whole contract. If the ticket has no Definition of done, use: "the reported behaviour no longer reproduces and a regression test covers it".

2. The diff

git diff origin/main...HEAD. Read every line. Note anything the ticket did not ask for.

3. The checks

Go: go vet and go test on the packages the diff changes, and on the packages that import a changed exported API. Add -race when the diff touches goroutines, locks or channels.
The full suite runs in the PR's CI, not here: gh pr checks <PR> (the PR is gh pr list --head <branch>). A red check is a finding; a pending one is an open item in your verdict, not a pass.
webapp_v2/: npm run lint and npm run build
Never skip, weaken or quarantine a test to get a pass.

4. The real flow

Start the stack and exercise the change as a user would.

Slot: use HOOPDEV_SLOT=N make run-dev so you do not stop another worktree's stack. The worktree's .env must carry that slot's API_URL and GRPC_URL and its own database.
A cloud sandbox: start Docker first (build-ticket, autonomous mode), then slots work as above. Without Docker, scripts/dev/run-sandbox.sh start runs one stack at a time: start, capture and stop each side in turn (--bin).
UI: drive Chrome.
CLI and protocols: the hoop binary against the local gateway only.

5. The evidence

Prove it the way a person would see it: the SAME flow on origin/main (one HOOPDEV_SLOT) and on the branch (another slot), same seed data.

Follow steps 1 to 3 of the evidence skill (.claude/skills/evidence/SKILL.md): plan one capture per Definition of done item on a surface a person meets (UI, API response, log line, CLI output), add the DURING DEPLOY case when there is a migration, wire or sidecar config change, and capture both sides.

Read the full file on GitHub · 104 lines

Changes

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.

3d ago Changed · +3 lines 8e9b1c4f2bfa
10d ago Changed · +5 lines · +2 tokens per session eb0ad7b8d019
13d ago First seen · 96 lines · 31 tokens per session scan A 2b9af19690dd

Subscribe to this mod's changes

qa is an agent published in the GitHub repository hoophq/hoop (837 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,073 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-10-14.

Code review LLM Security Testing agent databases grpc proxy

pr-test-analyzer

Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.

affaan-m/ECC · 24 tokens

Test Coverage

Ensure new functionality includes corresponding tests.

continuedev/continue · 9 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

hoop: Agent for Claude Code