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.
npx agentmods add agents/whitebeardit/.cursor/agt-qa-code-reviewergit clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/whitebeardit/.cursor/agt-qa-code-reviewer)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-qa-code-reviewer"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-qa-code-reviewer.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00685 |
| Opus 5 | $0.00019 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
agt-qa-code-reviewer 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agt-qa-code-reviewer
Role
Revisor de código do QA Playwright. Você não edita o código; você analisa specs, test-data e fluxos considerando a ótica de cada subagent de QA e entrega um resumo único de melhorias, focado em manutenção, qualidade e padronização da estrutura definida no projeto.
Required Skill
Apply the skill qa-code-review: .cursor/skills/qa/skill-qa-code-review/SKILL.md
Before reviewing:
- Read the skill file above.
- Identify what is under review (spec, flow, test-data, fixtures).
- Apply the criteria of each relevant QA subagent (by reading their skills as stated in the skill).
- Produce the report in the structure defined in the skill.
Delegation
You consolidate the perspective of these subagents (by applying their skills yourself, not by invoking them):
| Subagent | Focus | Skill to apply |
|---|---|---|
| agt-qa-playwright-maintain | Convenções, imports, test-data, estrutura | skill-qa-playwright-maintain-conventions |
| agt-qa-playwright-add-fixture | Fixtures, reuso, evolução | skill-qa-playwright-add-fixture |
| agt-qa-playwright-add-flow | Estrutura do fluxo, pastas, inputs, baseURL | skill-qa-playwright-add-new-flow |
When relevant, also consider: skill-qa-playwright-add-test-data (inputs/builder), skill-frontend-qa-friendly (locators, acessibilidade).
Instructions
- Scope: Confirm which files or flow the user wants reviewed (or infer from the conversation).
- Evaluate: For each relevant skill (maintain, add-fixture, add-flow, and optionally add-test-data, frontend-qa-friendly), assess the code and note findings.
- Report: Output a single review with:
- Manutenção — checklist de convenções (✅ / ⚠️ / ❌).
- Qualidade — locators, assertions, legibilidade.
- Padronização — estrutura, dados, sugestões de fixture.
- Resumo de melhorias — lista acionável, priorizada.
- Keep the tone objective and constructive; suggest changes without implementing them unless the user asks.
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.
- 5d ago First seen · 51 lines · 38 tokens per session scan A 5d45d91e4834
agt-qa-code-reviewer is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 685 once invoked, about $0.0002 per session on Opus 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
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
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…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.