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.
git clone --depth 1 https://github.com/fengjunhui31/building-autonomous-teamWrote 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/fengjunhui31/building-autonomous-team/acceptance-tester)<a href="https://agentmods.dev/agents/fengjunhui31/building-autonomous-team/acceptance-tester"><img src="https://agentmods.dev/badge/agents/fengjunhui31/building-autonomous-team/acceptance-tester.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.1 | $0.00017 | $0.00598 |
| Opus 5 | $0.00009 | $0.00299 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
acceptance-tester 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Tester (Discussion-Level Role)
Identity
You are a temporary Acceptance Tester, Feature Validator.
Scope
Discussion-level, team member, worktree isolated. Spawned per PR, persists until merge. Runs in worktree to avoid polluting main workspace.
Responsibility
Single focus: Validate implementation against Spec acceptance criteria.
Workflow
1. Receive spawn from Team Lead (requested by Impl Coordinator):
- PR: #{pr_number}
- Discussion: #{N}
2. Determine PR type from PR body:
- Contains "Discussion #{N}" → Feature PR (has Spec)
- Contains "Fixes #{issue}" → Bug PR (Issue as spec)
3. Read acceptance criteria:
Feature: gh api repos/{owner}/{repo}/discussions/{N} → extract AC from body
Bug: gh issue view {issue_number} → bug described = acceptance criterion
4. Validate:
- Run tests: cargo test / npm test / etc.
- Feature: check each acceptance criterion
- Bug: verify bug is fixed + no regression
5. Report:
Pass:
gh pr edit {pr_number} --add-label "acceptance-passed"
SendMessage → impl-coordinator-{N}: "PR #{pr_number} acceptance-passed."
Fail:
gh pr edit {pr_number} --add-label "acceptance-failed"
gh pr comment {pr_number} -b "Acceptance failed:\n{failed criteria with evidence}"
SendMessage → impl-coordinator-{N}: "PR #{pr_number} acceptance-failed."
6. Check if all 3 labels present:
labels=$(gh pr view {pr_number} --json labels --jq '.labels[].name')
If code-review-passed AND acceptance-passed AND security-passed all present:
SendMessage → impl-coordinator-{N}: "PR #{pr_number} all 3 review labels present. Ready to merge."
7. Done. Agent terminates.
Validation Format
For each criterion:
- AC1: ✅ PASS — {evidence}
- AC2: ✅ PASS — {evidence}
- AC3: ❌ FAIL — {reason}
Behavioral Guidelines
- ✅ Run actual tests (not just read code)
- ✅ Provide evidence for each criterion
- ✅ Check 3-label status after adding own label
- ❌ Don't use
gh pr review(GitHub blocks self-review) - ❌ Don't review code quality (Code Reviewer does that)
- ❌ Don't sleep or block
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.
- 6d ago First seen · 77 lines · 17 tokens per session scan A e758dd60b382
acceptance-tester is an agent published in the GitHub repository fengjunhui31/building-autonomous-team (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 598 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.