What is acceptance-test?

An automated check that tests whether a feature meets the conditions written in a GitHub issue. It can run integration and end-to-end tests, which check how several parts work together and how the feature works from a user's point of view.

Use it to create test scenarios from acceptance conditions, run them, verify every condition, and report the results.

It replaces uncertainty about whether an issue is complete with test results and collected evidence such as logs or screenshots.

acceptance-test — Command by Kewton

Install

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.

agentmods

npx agentmods add commands/kewton/commandmate/acceptance-test

Clone the repo

git clone --depth 1 https://github.com/Kewton/CommandMate

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 713 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00015	$0.00713
Opus 5	$0.00008	$0.00357
Sonnet 5	$0.00003	$0.00143
Haiku 4.5	$0.00002	$0.00071

Measured yesterday against content hash f72cf7bfbc17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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

.claude/commands/acceptance-test.md · 107 lines

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 が使用されます。

Changes

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.

yesterday First seen · 107 lines · 15 tokens per session scan B f72cf7bfbc17

Subscribe to this mod's changes

acceptance-test is a command published in the GitHub repository Kewton/CommandMate (39 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 713 once invoked, about $0.0001 per session on Opus 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.

Git and workflow Testing claude-code commandmate developer-tools git-worktree terminal tmux

crow-image

Show an image in Crow's Images panel — pass the file path as the argument.

corveil/crow · 16 tokens

release-notes

Draft release notes, recommend and apply a version bump, and update CHANGELOG.md for the next dormouse release by analyzing all merge commits and squash-merged PRs since the last release tag. Used as step 2 of the release checklist in docs/specs/deploy.md.

diffplug/dormouse · 60 tokens

acceptance-test