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 skills add reggiechan74/cc-plugins --skill acceptance-criteriagit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWrote 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/reggiechan74/cc-plugins/acceptance-criteria)<a href="https://agentmods.dev/skills/reggiechan74/cc-plugins/acceptance-criteria"><img src="https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/acceptance-criteria.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.00057 | $0.00831 |
| Opus 5 | $0.00028 | $0.00415 |
| Sonnet 5 | $0.00011 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
Acceptance Criteria 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 8d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Criteria: Define Success Before Execution
Purpose
Define specific, measurable acceptance criteria before any code execution, following test-driven development principles. Criteria serve as quality gates that critics evaluate with veto authority.
Criteria Requirements
Must be:
- Specific (not "good code" but "all 18 tests pass")
- Measurable (binary pass/fail)
- Pre-declared (before execution)
- Mapped to critics (clear validation responsibility)
Input Formats
Natural Language (Default)
/acceptance-criteria define for authentication refactoring:
- All existing tests must pass
- No OWASP Top 10 vulnerabilities
- Token storage uses httpOnly cookies
- Coverage maintains above 85%
Parsed automatically into structured format.
Structured YAML
criteria:
- name: Test Pass Rate
description: All existing auth tests pass
validator: code-critic
threshold: 100%
- name: Security Compliance
description: No OWASP Top 10 vulnerabilities introduced
validator: security-critic
checklist: OWASP-2021
- name: Code Coverage
description: Maintain test coverage
validator: code-critic
threshold: ">= 85%"
Template-Based
/acceptance-criteria use template financial
Loads pre-built criteria set for financial calculations.
Pre-Built Templates
Financial Template
---
domain: financial
criteria:
- Decimal precision maintained (no float arithmetic)
- Banker's rounding applied (IEEE 754)
- All operations logged to audit trail
- Results formatted to 2 decimal places
- Currency conversion explicit (no implicit conversions)
validators:
- domain-critic (financial specialization)
- code-critic (logic verification)
---
Security Template
---
domain: security
criteria:
- No SQL injection vectors (parameterized queries only)
- No XSS vulnerabilities (output escaping verified)
- Authentication bypass prevented (auth required on protected routes)
- HTTPS enforced (no plaintext transmission)
- Secrets not in code (environment variables used)
- Password hashing with bcrypt/argon2
validators:
- security-critic
- code-critic (implementation check)
---
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.
- 8d ago First seen · 156 lines · 57 tokens per session scan A e488faa6bf0f
Acceptance Criteria is a skill published in the GitHub repository reggiechan74/cc-plugins (7 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 831 once invoked, about $0.0003 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 skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.