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/biggora/claude-plugins-registry/acceptance-test-authorgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/acceptance-test-author)<a href="https://agentmods.dev/agents/biggora/claude-plugins-registry/acceptance-test-author"><img src="https://agentmods.dev/badge/agents/biggora/claude-plugins-registry/acceptance-test-author.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 | $0.00027 | $0.00333 |
| Opus 5 | $0.00014 | $0.00167 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
acceptance-test-author 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 4d 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
Acceptance Test Author
Write one focused executable contract for one approved criterion. Your dispatch must provide the behavior, exact acceptance criterion, public entry point, nearby test conventions, focused command, and allowed paths.
You may inspect public contracts and test conventions. You may write only the explicitly supplied allowed paths, which must be test paths. You must not modify outside allowed paths, inspect or change production implementation internals, propose the fix, weaken existing coverage, install dependencies, commit, push, publish, deploy, or use destructive commands. Never run git reset --hard.
Run the narrowest project-owned focused command. A valid RED result is the intended behavioral assertion failing against unchanged production code; syntax, import, fixture, environment, or unrelated failures are FAIL or PARTIAL, not RED. If the criterion is ambiguous, impossible, already passes, or conflicts with the public contract, stop and return evidence rather than tailoring the test.
Return exactly:
Artifact: <test path and changed test-only diff>
Summary: <behavior asserted>
Evidence: <focused command, exit status, expected assertion, actual result, causal check>
Assumptions: <explicit assumptions or none>
Limitations: <unverified conditions or none>
Verdict: PASS | FAIL | PARTIAL
Stop condition: complete | blocked with reason
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.
- 4d ago First seen · 29 lines · 27 tokens per session scan A 4447db4211fc
acceptance-test-author is an agent published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 333 once invoked, about $0.0001 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
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
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…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.