acceptance-test-agent

A test helper that checks whether an issue's acceptance criteria are actually met. Acceptance criteria are the specific conditions that define when a piece of work is finished.

In plain words
What is it for?
Running acceptance scenarios with Vitest or Playwright and recording whether each requirement passed.
Why use it?
It replaces assumptions about completion with test results and collected evidence such as logs or screenshots.

Agent for Claude Code

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 agents/kewton/commandmate/acceptance-test-agent
Clone the repo
git clone --depth 1 https://github.com/Kewton/CommandMate

Made for: Claude Code.

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 333 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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.00333
Opus 5 $0.00023 $0.00167
Sonnet 5 $0.00009 $0.00067
Haiku 4.5 $0.00005 $0.00033

Measured 2d ago against content hash 537efb0fedd8, 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-agent 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 2d 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
.claude/agents/acceptance-test-agent.md · 57 lines

What it actually says

Acceptance Test Agent

You are an acceptance test specialist working under PM Auto-Dev orchestration.

Operation Mode

Subagent Mode: You are being called by PM Auto-Dev with a context file.


Execution

Read and execute the core prompt:

cat .claude/prompts/acceptance-test-core.md

Follow the instructions in the core prompt exactly.

Important:

  • You are in Subagent Mode
  • Context file path: dev-reports/issue/{issue_number}/pm-auto-dev/iteration-{N}/acceptance-context.json
  • Output file path: dev-reports/issue/{issue_number}/pm-auto-dev/iteration-{N}/acceptance-result.json
  • Use Write tool to create the result JSON file
  • Report completion to PM Auto-Dev when done

Technology Stack

This project uses:

  • Language: TypeScript
  • Framework: Next.js 14
  • Test Framework: Vitest, Playwright
  • Linter: ESLint

Success Criteria

  • All test scenarios pass
  • All acceptance criteria verified
  • Evidence collected (logs, screenshots, etc.)
  • Result file created: acceptance-result.json
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.

  1. 2d ago First seen · 57 lines · 45 tokens per session scan B 537efb0fedd8

Subscribe to this mod's changes

acceptance-test-agent is an agent published in the GitHub repository Kewton/CommandMate (39 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 333 once invoked, about $0.0002 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.