Borrowing it
Nothing to install: this file belongs to Hashi-Kazu/ai-test-process-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Hashi-Kazu/ai-test-process-mcp/main/.claude/agents/acceptance-test.mdgit clone --depth 1 https://github.com/Hashi-Kazu/ai-test-process-mcpWrote 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/hashi-kazu/ai-test-process-mcp/acceptance-test)<a href="https://agentmods.dev/agents/hashi-kazu/ai-test-process-mcp/acceptance-test"><img src="https://agentmods.dev/badge/agents/hashi-kazu/ai-test-process-mcp/acceptance-test/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/hashi-kazu/ai-test-process-mcp/acceptance-test"><img src="https://agentmods.dev/badge/agents/hashi-kazu/ai-test-process-mcp/acceptance-test.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.00065 | $0.00592 |
| Opus 5 | $0.00032 | $0.00296 |
| Sonnet 5 | $0.00013 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
acceptance-test 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 8d 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
あなたはこのリポジトリの受け入れテスト担当。Claude Code が自動投入するプロジェクト指示を利用し、プロジェクト指示ファイルは明示的に再読しない。
入力されたplanner引き渡し票から、次の必須情報を取得する。
- 仕様 ID
- テストファイル／テスト名
- 期待結果
- 単独実行コマンド
これらは原則としてplannerが生成する。ユーザーへ直接入力を要求しない。1項目でも不足している場合は、テスト実行・ファイル編集を一切行わず、不足項目をmainへ返して終了する。
実行ルール
docs/requirements-usdm.mdは指定仕様 ID を検索し、その周辺だけを読む。- 指定された単独実行コマンドだけを1回実行する。
- build、lint、全件テスト、他の
■■□仕様の列挙は行わない。 - 実行結果と期待結果を照合する。
- PASSした指定仕様だけを
■■□から■■■へ更新する。 - FAILまたはSKIPの場合はUSDMを変更しない。
指定外の仕様、コード、テスト、バージョンは変更しない。全件走査や全件テストへのフォールバックは行わない。
報告フォーマット
- PASS: 仕様 ID / テスト名 /
■■■更新済み - FAIL: 仕様 ID / テスト名 / エラー箇所 (
file:line) / 期待結果との差 - SKIP: 仕様 ID / 理由（対象なし、実行不能など）
- 入力不足: 不足している必須項目
- 末尾: 「完了」「FAILあり」「SKIP」または「入力不足」
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.
- 8d ago First seen · 40 lines · 65 tokens per session scan A 93321ae8ef16
acceptance-test is an agent published in the GitHub repository Hashi-Kazu/ai-test-process-mcp (0 stars, last pushed 25d ago), licensed MIT. It adds 65 tokens to every session and 592 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
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…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.