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/ayoubben18/ab-method/critique-plannpx skills add ayoubben18/ab-method --skill critique-plangit clone --depth 1 https://github.com/ayoubben18/ab-methodWrote 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/ayoubben18/ab-method/critique-plan)<a href="https://agentmods.dev/skills/ayoubben18/ab-method/critique-plan"><img src="https://agentmods.dev/badge/skills/ayoubben18/ab-method/critique-plan.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.00086 | $0.01223 |
| Opus 5 | $0.00043 | $0.00611 |
| Sonnet 5 | $0.00017 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
critique-plan 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critique Plan (pre-implementation)
Stress-test a drafted plan against the project's domain model before any code is written. This skill produces pushbacks, not suggestions — it never gold-plates a plan that is already sound.
Silence is the expected outcome. A plan that speaks the canonical language and respects the documented decisions gets a one-line "No objections." Do not manufacture concerns to look thorough.
ALWAYS check .ab-method/structure/index.yaml FIRST for where the domain model lives — paths are
user-configurable.
"The plan" is the drafted mission list (from create-task), the task DAG (from create-roadmap), or whatever the user pastes in (standalone).
Process
1. Load the domain model
Read only what exists; skip missing files silently (don't flag them or offer to create them):
UBIQUITOUS_LANGUAGE.md, CONTEXT.md (or CONTEXT-MAP.md + each src/<context>/CONTEXT.md),
docs/adr/, and docs/architecture/*.
2. Spin up ONE read-only domain critic (subagent)
Spawn a single subagent — domain-critic — with the plan verbatim, the files from Step 1, and the rule
that it is read-only: it returns pushbacks as text and edits nothing. Isolating it keeps the critique
out of the planning context. Its brief:
Fire ONLY on a genuine conflict, one of:
- Terminology drift — the plan names a concept differently from the glossary/
CONTEXT.md, or reuses a canonical term for a new meaning. - Wrong bounded context — work placed in the wrong context, or a unit that straddles a documented boundary.
- Contradicts an ADR — reverses a recorded decision and the friction is real enough to reopen it.
Cite
ADR-NNNN. - Bad graph seam (roadmap) — a
depends-onedge crosses a seam the wrong way, two "independent" tasks share a domain concept, or a task is mis-scoped (an epic, or a single mission dressed as a task). - Reinvents a named concept — introduces a new abstraction for something the domain model names.
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 · 81 lines · 86 tokens per session scan A 46e8128bee33
critique-plan is a skill published in the GitHub repository ayoubben18/ab-method (189 stars, last pushed 4d ago), licensed MIT. It adds 86 tokens to every session and 1,223 once invoked, about $0.0004 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
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…