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 skills/firstp1ck/pi-coding-agent-forge/acceptance-testernpx skills add Firstp1ck/pi-coding-agent-forge --skill acceptance-testergit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/skills/firstp1ck/pi-coding-agent-forge/acceptance-tester)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/acceptance-tester"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/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 | $0.00046 | $0.00862 |
| Opus 5 | $0.00023 | $0.00431 |
| Sonnet 5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
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 5d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Tester
Final quality gate — determines whether a project is ready to proceed.
Acceptance Criteria Source
The definition of done comes from the combined plan (section 8), which typically includes:
- All modules implemented
- All tests passing
- Linting clean
- Application starts and core flows work
- Documentation updated
- Security constraints verified
Acceptance Checklist
Run through this checklist systematically:
1. Build Verification
- Project builds without errors
- No compiler/linter warnings (or all are documented exceptions)
- All dependencies resolve correctly
2. Test Suite
- Full test suite passes (
cargo test/npm test/pytest) - Coverage meets target from combined plan (default: 80%)
- No skipped or ignored tests without documented reason
3. Core Flow Verification
For each core user flow defined in the spec:
- Happy path works end-to-end
- Primary error paths handled gracefully
- Data persists correctly across operations
4. Spec Completeness
- All P0 spec requirements verified (from spec-vs-impl checker)
- No Blocker or Critical bugs outstanding
- All Major bugs either fixed or explicitly deferred with user approval
5. Security Constraints
For each constraint from Zero's review:
- Constraint is implemented
- Constraint is tested
- No obvious bypasses found during functional testing
6. Integration Points
- Cross-module integrations work correctly
- Error propagation across module boundaries is handled
- Data format consistency across interfaces
Verdict Determination
PASS — Ready for Next Phase
All of these must be true:
- Build succeeds
- All tests pass
- Coverage target met
- Zero Blocker bugs
- Zero Critical bugs
- All P0 spec requirements verified
- All security constraints verified
CONDITIONAL PASS
- Minor or some Major bugs remain but none are blockers
- User has approved deferring specific issues to v2
- Core flows work, edge cases may have issues
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.
- 5d ago First seen · 125 lines · 46 tokens per session scan A dc32a422776b
acceptance-tester is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (77 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 862 once invoked, about $0.0002 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-30.
Other skills, from other repositories
Avant-Garde Frontend Architect
Expert frontend design and UI implementation with a focus on bespoke, visually striking, and minimalist interfaces. Trigger with 'ULTRATHINK' prefix for deep architectural analysis. Automatically detects and uses existing UI libraries (Shadcn UI, Radix, MUI) while applying unique styling. Includes a personalized…
FPEF Evidence Analyzer
Systematic Find-Prove-Evidence-Fix framework for complex system analysis and intervention. Use when debugging failures, investigating incidents, analyzing performance issues, or optimizing complex systems.
MCP Universal Manager
Auto-discovery and health monitoring for MCP servers across Claude Code, Factory Droid, Antigravity, Gemini, and other AI platforms. Use when managing MCP servers, monitoring tool integration, or debugging MCP connectivity issues.
council
Run a 5-adviser council to stress-test any decision. Five distinct lenses (Contrarian, First-Principles, Expansionist, Outsider, Executor) answer independently, then anonymously peer-review each other, and a Chairman synthesizes a single clear recommendation. Kills sycophancy and groupthink on high-stakes calls.
UltraPlan Autonomous Planner
Advanced autonomous planning system with viral automation, predictive support, and $100M ARR methodology. Use when creating strategic plans, scaling operations, or implementing autonomous business systems.
compound-engineering
Orchestration layer that coordinates Debt-Sentinel, Red Team Tribunal, and Spec-Lock into unified workflows. Use when you need comprehensive quality assurance with multiple validation stages. Provides safe-edit workflows, CI pipelines, enhancement pipelines, and engineering metrics dashboard.