agentmods.dev

shipkit-review-planning

shipkit-review-planning is a skill for Claude Code from stefan-stepzero/shipkit. It costs 52 tokens per session (1,126 once invoked), scanned A, original, MIT.

An internal review skill for checking whether planning documents agree with one another. It compares the technology stack, codebase summary, roadmap, feature specifications, implementation plans, tests, and manual tasks.

In plain words
What is it for?
Use it as a review gate for a project’s planning phase, not as a direct development tool.
Why use it?
It helps reveal missing features, plans, tests, or links between product requirements and engineering work.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: agent in frontmatter.

not rated 1 1mo ago A scan 52 tokens original MIT
View the source file stefan-stepzero/shipkit
Install

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.

agentmods
npx agentmods add skills/stefan-stepzero/shipkit/shipkit-review-planning
Any agent
npx skills add stefan-stepzero/shipkit --skill shipkit-review-planning
Clone the repo
git clone --depth 1 https://github.com/stefan-stepzero/shipkit

Made for: Claude Code.

Wrote 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.

agentmods badge for shipkit-review-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-review-planning.svg)](https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-review-planning)
Your own site
<a href="https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-review-planning"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-review-planning.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,126 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01126
Opus 5 $0.00026 $0.00563
Sonnet 5 $0.00010 $0.00225
Haiku 4.5 $0.00005 $0.00113

Measured 5d ago against content hash edd111da1b23, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

shipkit-review-planning 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.

install/skills/shipkit-review-planning/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

shipkit-review-planning - Planning Assessment

Purpose: Read all planning artifacts and cross-reference them for alignment. Write a structured assessment for the planning orchestrator.

Input

Required artifacts (the planning phase must produce all of these):

  • .shipkit/stack.json
  • .shipkit/codebase-index.json
  • .shipkit/spec-roadmap.json
  • .shipkit/specs/*.json — at least one spec per roadmap item
  • .shipkit/plans/*.json — at least one plan per spec
  • .shipkit/test-cases/ — test specifications
  • .shipkit/user-tasks.json — manual user tasks

Direction context (produced by prior loop, read for cross-reference):

  • .shipkit/why.json
  • .shipkit/product-definition.json, .shipkit/engineering-definition.json
  • .shipkit/architecture.json
  • .shipkit/goals/strategic.json, .shipkit/goals/product.json, .shipkit/goals/engineering.json

Alignment Checks

  1. Completeness: Are ALL required planning artifacts present? Missing artifacts are gaps.

  2. Product ↔ Engineering: Every product feature has a corresponding mechanism?

  3. Definition ↔ Specs: Every defined feature has a spec?

  4. Specs ↔ Roadmap: Roadmap includes all specs with sensible priority?

  5. Plans ↔ Specs: Every spec has a plan? Plans reference the correct spec?

  6. Stage alignment: Specs and plans scoped for current stage?

  7. Goal coverage: Specs, if implemented, satisfy product and engineering goals?

  8. Architecture consistency: Do plans align with architecture.json decisions?

  9. Prerequisites by phase: Group blocking user tasks by their blocksPhase value. Report separately:

    • Current-phase blockers (tasks where blocksPhase matches why.json current stage AND blocking: true)
    • Future-phase blockers (tasks where blocksPhase is a later stage)
    • General tasks (tasks where blocksPhase is null)

    Only current-phase blockers count as blocking prerequisites. Future-phase tasks are informational — do NOT count them in the blocker total. If a task has no blocksPhase field (legacy format), infer from context or treat as current-phase.

Read the full file on GitHub · 98 lines

Changes

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.

  1. 5d ago First seen · 98 lines · 52 tokens per session scan A edd111da1b23

Subscribe to this mod's changes

shipkit-review-planning is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,126 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.

Code reviewPlanningai-toolsanthropicclaudeclaude-codeclaude-skillsdeveloper-tools
Related

Other skills, from other repositories

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

market-research-workflow

Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…

1102tools-dev/federal-contracting-skills · 159 tokens

acquisition-policy-workflow

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…

1102tools-dev/federal-contracting-skills · 115 tokens

igce-builder-cr

Trigger for: cost-reimbursement IGCE, CR cost estimate, CPFF, CPAF, CPIF, cost-plus estimate, BAA estimate, fixed-fee analysis, award-fee analysis, incentive-fee analysis, proposed CR rate validation, cost-pool buildup, share-ratio scenario, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable…

1102tools-dev/federal-contracting-skills · 161 tokens

igce-builder-lh-tm

Trigger for: Labor-Hour IGCE, LH estimate, Time-and-Materials IGCE, T&M estimate, burdened hourly rate, burden multiplier, labor-category ceiling hours, materials estimate, proposed LH/T&M rate validation, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable LH/T&M estimates using BLS OEWS…

1102tools-dev/federal-contracting-skills · 147 tokens

ot-project-description-builder

Trigger for: OT project description, OTA scope, Research OT under 10 U.S.C. 4021, Prototype OT under 10 U.S.C. 4022, follow-on production scope under 10 U.S.C. 4022(f), milestone-based project scope, prototype objective, phase or go/no-go structure, BAA white-paper conversion, SOO conversion, transition planning, or…

1102tools-dev/federal-contracting-skills · 185 tokens