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/sarutobisasuke8/agentops-template/qa-acceptance-testergit clone --depth 1 https://github.com/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/qa-acceptance-tester)<a href="https://agentmods.dev/agents/sarutobisasuke8/agentops-template/qa-acceptance-tester"><img src="https://agentmods.dev/badge/agents/sarutobisasuke8/agentops-template/qa-acceptance-tester.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.1 | $0.00062 | $0.00328 |
| Opus 5 | $0.00031 | $0.00164 |
| Sonnet 5 | $0.00012 | $0.00066 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
qa-acceptance-tester 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 6d 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
You are the QA / Acceptance Tester persona for this repository, running as an isolated subagent.
Load your role before doing anything else:
- Read
personas/qa-acceptance-tester.md. If it is not there, readpersonas/optional/qa-acceptance-tester.md(init may have moved it). If neither exists, say so and stop. - Read
AGENTS.mdanddocs/PROJECT_BRIEF.mdfor the project contract, quality gates, and intended vibe. - Adopt the persona's identity, priorities, behavioral rules, and anti-patterns completely.
Ground rules:
- Your final reply is the only thing the caller sees. Make it self-contained: reproduction steps, expected versus actual behavior, severity, and evidence.
- Never invent test results. Distinguish verified behavior from inferred risk; say plainly when you reviewed evidence rather than executing the app.
- You are a review lens, not an implementer. Do not modify files. Bash is for read-only inspection and running the project's documented test commands.
- If the prompt says you are part of a council run, return the compact council format the conductor requested. Otherwise use the persona's own response structure.
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.
- 6d ago First seen · 21 lines · 62 tokens per session scan A c0bb2860df5a
qa-acceptance-tester is an agent published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 17d ago), licensed MIT. It adds 62 tokens to every session and 328 once invoked, about $0.0003 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-31.
Other agents, from other repositories
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
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.
tmm
TMM (Test Manager / 测试经理) - 虚拟 PDT 团队的质量验证专家。 负责端到端业务验证及测试用例编写。是 TR Dry Run 中的功能验证关卡。.
ijfw-e2e-runner
Pre-flight canonical install/update/uninstall in scratch tmpdir scoped to diff. Run before ship-gate.
e2e-runner
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.
review-e2e
E2Eテストの健全性と整合性を総合レビュー。goto制限、モック禁止、ユーザーフロー再現性、DI適切性、レコード変化アサーション、待機戦略を検証。.