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 uta2000/feature-flow --skill verify-acceptance-criteriagit clone --depth 1 https://github.com/uta2000/feature-flowWrote 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/uta2000/feature-flow/verify-acceptance-criteria)<a href="https://agentmods.dev/skills/uta2000/feature-flow/verify-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/uta2000/feature-flow/verify-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.00059 | $0.03242 |
| Opus 5 | $0.00030 | $0.01621 |
| Sonnet 5 | $0.00012 | $0.00648 |
| Haiku 4.5 | $0.00006 | $0.00324 |
Grade A, and why
verify-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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Acceptance Criteria
Mechanically checks all acceptance criteria from an implementation plan against the actual codebase. Delegates verification to the task-verifier agent and reports results.
Announce at start: "Running verify-acceptance-criteria to check implementation against the plan."
When to Use
- After implementing one or more tasks from a plan
- Before claiming work is complete
- Before committing or creating a PR
Optional Args (used when invoked from orchestrator dispatch)
When invoked as a Pattern B consolidator subagent (per #251 Wave 3 phase 4), the orchestrator passes these arguments so the skill can skip the hoisted task-verifier dispatch and write its structured return contract back to a tmp JSON file:
verifier_report_path: <absolute-path-to-report-md>— when set, the skill skips Step 3'stask-verifierdispatch (the orchestrator has already executed it) and reads the pre-written verification report from this Markdown file. The report follows the format defined inagents/task-verifier.mdStep 4.write_contract_to: <absolute-path-to-json>— when set, writes the structured return contract directly to this JSON file path after Step 4 (Present Results) completes (see Step 6 below). Unlikedesign-document, this is a plain JSON file path, not a state-file YAML path. verify-acceptance-criteria does not own aphase_summariesbucket — see "Why no state-file write" below.
Both args are optional. If verifier_report_path is absent, Step 3 dispatches the task-verifier as before. If write_contract_to is absent, Step 6 is skipped — the skill behaves identically to its inline-invocation form.
Why no state-file write: the four phase_summaries buckets (brainstorm, design, plan, implementation) are all claimed by phase-boundary writes. Verify-acceptance-criteria is a verification step within the implementation phase, not a phase that owns a bucket; reusing implementation.return_contract would collide with the future Phase 6 (subagent-driven-development) Pattern B contract. The contract is consumed once by the orchestrator's validator and discarded — no cross-compaction reader needs it from the state file.
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 · 264 lines · 59 tokens per session scan A 6c124da2685d
verify-acceptance-criteria is a skill published in the GitHub repository uta2000/feature-flow (4 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 3,242 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
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.