Borrowing it
Nothing to install: this file belongs to Kewton/CommandMate. 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/Kewton/CommandMate/main/.claude/commands/acceptance-test.mdgit clone --depth 1 https://github.com/Kewton/CommandMateWrote 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/commands/kewton/commandmate/acceptance-test)<a href="https://agentmods.dev/commands/kewton/commandmate/acceptance-test"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/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/commands/kewton/commandmate/acceptance-test"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/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.00015 | $0.00713 |
| Opus 5.5 | $0.00006 | $0.00285 |
| Sonnet 5.5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade B, and why
acceptance-test scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/prompts/acceptance-test-core.md What it actually says
受入テストスキル
概要
Issue要件に基づいて受入テスト（Acceptance Test）を自動実行し、すべての受入条件が満たされていることを検証するスキルです。
このスキルはスラッシュコマンドモードで動作します（ユーザーが直接実行）。
使用方法
/acceptance-test [Issue番号]- 「Issue #[番号]の受入テストを実行してください」
- 「[機能名]の受入条件を検証してください」
実行内容
共通プロンプトを読み込んで実行します:
cat .claude/prompts/acceptance-test-core.md
↑ このプロンプトの内容に従って、受入テストを実行してください。
動作モード
スラッシュコマンドモード:
- ユーザーから対話的に情報を取得
- Issue番号、受入条件、テストシナリオなどを確認
- 結合テスト/E2Eテストを実行
- 結果をターミナルに表示
テストシナリオ作成
受入条件に基づいてテストシナリオを作成：
// tests/integration/xxx.test.ts
import { describe, it, expect } from 'vitest'
describe('Feature: [機能名]', () => {
it('シナリオ1: [シナリオ説明]', async () => {
// Given: 前提条件
// When: 操作
// Then: 期待結果
})
})
完了条件
以下をすべて満たすこと：
- すべてのテストシナリオが成功
- すべての受入条件が検証済み
- エビデンスが収集済み（ログ、スクリーンショットなど）
出力例
受入テスト完了
## 機能概要
新機能の追加
## テストシナリオ結果
シナリオ1: 正常系のテスト
- test_scenario_1: PASSED
シナリオ2: エラー系のテスト
- test_scenario_2: PASSED
## 受入条件検証
- 条件1を満たしていること
- 条件2を満たしていること
## エビデンス
- テスト結果ログ: test_results.log
- すべてのテストケース成功: 5/5
すべての受入条件を満たしています
サブエージェントモード
サブエージェントとして呼び出す場合は、PM Auto-Devが以下のように実行します：
Use acceptance-test-agent to verify Issue #166 acceptance criteria.
この場合、.claude/agents/acceptance-test-agent.md が使用されます。
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 · 107 lines · 15 tokens per session scan B f72cf7bfbc17
acceptance-test is a command published in the GitHub repository Kewton/CommandMate (44 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 713 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
qa-pr
Device-test a GitHub pull request on iOS simulator, Android emulator, and/or physical device. Installs the PR head via rn-dev-agent and reports pass/fail with repro steps and screenshots.
ux-grill
Use when a running web app's UX has to be audited reproducibly rather than by feel — a deterministic mechanical pass over routes and viewports (axe, target size, horizontal overflow, page title, scripted journeys) followed by a screenshot-grounded interrogation of the operator, journey by journey, with two persona…
test
Agentic end-to-end test orchestrator — drive web/macOS flows, evaluate UX rubric, reconcile issues.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
lock-e2e
Promote a verified action into a frozen, locked e2e regression test. Runs the action once strict (no repair) via cdplocke2etest and freezes it to .rn-agent/e2e/ .yaml only if it passes. v1 supports param-free actions only.