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 tomzx/agents --skill review-plangit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/review-plan)<a href="https://agentmods.dev/skills/tomzx/agents/review-plan"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tomzx/agents/review-plan"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-plan.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.01297 |
| Opus 5.5 | $0.00008 | $0.00519 |
| Sonnet 5.5 | $0.00004 | $0.00259 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
review-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 20d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Plan
Reviews an implementation plan and reports findings across six categories: completeness, feasibility, dependencies, risk coverage, timeline realism, and reversibility.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. .sdlc/features/N-<slug>/plan.md(unified) or.sdlc/features/N-<slug>/plan/index.mdplus its siblingplan/<concern>.mdfiles (split), or an implementation plan provided in context or as a file path.sdlc/features/N-<slug>/specification.md(optional, improves coverage analysis)
Steps
- Resolve the plan. Look for
.sdlc/features/N-<slug>/plan.mdfirst; if absent, look for.sdlc/features/N-<slug>/plan/index.mdand read it together with everyplan/<concern>.mdit lists. Otherwise read from context or as a file path. Treat the whole plan set (index + concern files) as the unit under review. - Cross-reference against the specification or requirements if available.
- Run the deterministic checker when possible: render each
mermaidblock withmmdc(ornpx -y @mermaid-js/mermaid-cli) when available. A tool that is not installed is skipped (never blocks); a render failure is a blocking finding under Dependencies or Timeline Realism. - Identify issues in each category below.
For a split plan, also check that
plan/index.mdaggregates milestones, cross-concern dependencies, risks, and timeline consistently with the concern files. - Report findings. Omit any category that has no findings.
- Write the findings to
.sdlc/features/N-<slug>/review-plan.mdwith frontmatterartifact: plan,verdict(approvedif there are no blocking findings,changes-requestedif the author must address findings,rejectedfor a fundamental flaw), andreviewed_at: <ISO date>, and the findings as the body, perskills/sdlc/references/shared.md. Record any unresolved open questions in the findings body. For any question that carries meaningful risk to the implementation, also invoke/create-assumptionto record it formally.
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.
- 20d ago Changed · +1 lines 0a93df5fb112
- 22d ago Changed · +4 lines 02cde2fda55c
- 24d ago Changed 117a39770ef8
- 1mo ago First seen · 123 lines · 19 tokens per session scan A 08b66c165f4f
review-plan is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,297 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.