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/uta2000/feature-flow/verify-plan-criterianpx skills add uta2000/feature-flow --skill verify-plan-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-plan-criteria)<a href="https://agentmods.dev/skills/uta2000/feature-flow/verify-plan-criteria"><img src="https://agentmods.dev/badge/skills/uta2000/feature-flow/verify-plan-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.00042 | $0.04678 |
| Opus 5 | $0.00021 | $0.02339 |
| Sonnet 5 | $0.00008 | $0.00936 |
| Haiku 4.5 | $0.00004 | $0.00468 |
Grade A, and why
verify-plan-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 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Plan Criteria
Validates that every task in an implementation plan has machine-verifiable acceptance criteria. For tasks missing criteria, drafts them automatically from the task's context and presents them for approval.
Announce at start: "Running verify-plan-criteria to check acceptance criteria coverage."
When to Use
- After writing an implementation plan
- Before the user reviews and approves a plan
- When reviewing an existing plan for feature-flow compliance
Optional Output Args (used when invoked from orchestrator dispatch)
When invoked as a Pattern A subagent dispatch (per #251), the orchestrator passes two additional arguments so the skill can write its structured return contract back to the lifecycle's in-progress state file:
write_contract_to: <absolute-path-to-in-progress-yml>— when set, writes the return contract tophase_summaries.<phase_id>.return_contractin that YAML file after Step 6 (see Step 7 below).phase_id: <bucket-name>— identifies whichphase_summariesbucket to write into. Must be one of the four fixed buckets defined in the in-progress state-file schema:brainstorm,design,plan, orimplementation. If absent whenwrite_contract_tois set, defaults toplan(the bucket that contains theverify-plan-criterialifecycle step). Do not confusephase_idwith the contract's ownphasefield —phase_idis the bucket key, the contract'sphasefield is the lifecycle step name (verify-plan-criteria) per #251's locked spec.
Both args are optional. If write_contract_to is not present in ARGUMENTS, Step 7 is skipped — the skill behaves identically to its inline-invocation form.
Format Detection
Before parsing, determine which format the plan file uses:
See references/xml-plan-format.md for the canonical specification and complete field reference.
See references/xml-plan-format-runtime.md for the detection algorithm, error handling rules, and edge cases.
- Read the first 50 lines of the plan file
- Track code-fence state: toggle
in_fenceon each line that starts with``` - For each non-fenced line: check if it matches
/^<plan version="/ - If match found → XML mode
- Before committing to XML mode: scan the full file for
</plan>. If absent → log warning "plan appears truncated — treating as prose" and use Prose mode - If no match in first 50 lines → Prose mode (existing behavior unchanged)
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 · 346 lines · 42 tokens per session scan A 3225c2727d24
verify-plan-criteria is a skill published in the GitHub repository uta2000/feature-flow (4 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 4,678 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…