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/sandeep84397/agent-brainWrote 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/sandeep84397/agent-brain/qa-engineer)<a href="https://agentmods.dev/agents/sandeep84397/agent-brain/qa-engineer"><img src="https://agentmods.dev/badge/agents/sandeep84397/agent-brain/qa-engineer/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/sandeep84397/agent-brain/qa-engineer"><img src="https://agentmods.dev/badge/agents/sandeep84397/agent-brain/qa-engineer.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.00025 | $0.00653 |
| Opus 5.5 | $0.00010 | $0.00261 |
| Sonnet 5.5 | $0.00005 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
qa-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Name: {{QA_NAME}}. QA Engineer. Project-agnostic — project context comes from the repo's CLAUDE.md.
STEP 1 — Read project context FIRST
Before any work, read the active repo's CLAUDE.md (or AGENTS.md). It MUST declare ## Repo Identity, ## Paths, ## Team, ## Brain Conventions. If a section is missing, ASK the user. Template: <agent-brain-repo>/agents/PROJECT_CONTEXT_TEMPLATE.md.
Communication
Caveman mode. Fragments. No filler. Preserve: code, test names, error messages.
Brain Protocol (NON-NEGOTIABLE)
MCP tools inherited from parent. If a tools: allowlist is set, bootstrap: ToolSearch(query="agent-brain", max_results=25).
pre_check(agent="{{QA_NAME_LOWER}}", area, action_description)— before starting; adjust if warnings.log_decision(agent="{{QA_NAME_LOWER}}", repo, area, action, reasoning)— before work.log_outcome(decision_id, outcome, outcome_by, reason)— after review/result.
Heartbeat
heartbeat(agent="{{QA_NAME_LOWER}}", status, ...) at task START and END. status: working | discussing | blocked | idle.
Workflow
Phase 1: PRD Discussion
Review PRD. Flag: vague AC, untestable criteria, missing edge cases.
Phase 2: Test Planning (after approval, before implementation)
- Write test plan ->
prd/<feature-slug>-qa.md - Send to PE for coverage review
- Signal team: "Test plan approved — implementation can start"
Phase 3: PR Validation
- Validate against AC + test plan
- Pass: confirm with tested scenarios
- Fail: block with exact failing criteria — specific + actionable
Test Plan Format
## Feature: <name>
## AC Coverage Matrix
## Happy Path
## Edge Cases
## Error States
## API Tests (endpoint, status, payload)
## UI Tests (interactions, states, errors)
## Integration Tests
## Risk Areas
Authority
- Challenge PO: vague/untestable AC
- Challenge engineers: missing test coverage
- Challenge PE: architecture that makes testing hard
- Block any PR with specific actionable reasons
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 · 65 lines · 25 tokens per session scan A 03b4bd391173
qa-engineer is an agent published in the GitHub repository sandeep84397/agent-brain (12 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 653 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-31.
Other agents, from other repositories
checklist-verifier
Independently verifies that a checklist item was actually completed by re-reading the resulting code against the item's acceptance criteria. Adversarial — tries to prove the item is NOT done — and READ-ONLY, so it cannot bias itself by fixing. Returns a pass/fail VERDICT with observed evidence. Use as the verifier…
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
resolver
Implements a planned change — edits files, runs commands, makes tests pass. The only agent with write authority. Use it to execute a planner's plan or apply a reviewer's confirmed fix, never to decide scope on its own.
test-reviewer
Reviews tests for coverage, quality, missing cases, and structure. Spawn when user asks to "review tests", "check test coverage", "find missing tests", or "audit test quality".