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/scolladon/craft/planningnpx skills add scolladon/craft --skill planninggit clone --depth 1 https://github.com/scolladon/craftWrote 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/scolladon/craft/planning)<a href="https://agentmods.dev/skills/scolladon/craft/planning"><img src="https://agentmods.dev/badge/skills/scolladon/craft/planning.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.00030 | $0.00534 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
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 4d 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.
What it actually says
craft:planning
Preamble (always runs — non-overridable)
- Manifest read (lint if standalone).
- Probe: plan directory (
paths.plan, elsedocs/plan/, create if absent); design doc present? present → hard input; absent → the planner's mandatory input is the resolved brief and it performs its own exploration (slower, never blocked). - Memory read/write surface (advisory).
READS:
part-sizingentries from prior runs as a weak planner hint (no per-use re-check; confidence-weighted). Prepended to the planner spawn's injected block when non-empty. WRITES: none directly from this phase — part sizing is observed at implementation when each part's pass/blocked outcome is known. - Intention consult surface (advisory). The phase receives the intention consult
slice on slot 1 — the
IntentionViewentries whose subjects intersect this phase's change scope, prepended into the same injected contract block as the memory hint (seeskills/run/SKILL.mdstep 4). An empty slice means the phase probes as today.
Procedure (default body — a manifest override: replaces everything below)
- Spawn craft:planner with: the design doc path (or brief) + the accepted ADR paths; the
absolute working directory; the output path
<plan-dir>/<slug>.md; the template"${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/templates/plan.md"; the part-gate command (manifestgates.part, or probe: the repo's test runner over touched files, falling back togates.phase); the commit messagedocs(plan): <slug>; global + planning-phasecontext:files verbatim. - When it returns: run
"${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/plan-lint.sh" <plan-path>— the phase cannot close red. On failure, respawn fresh with the lint output; ≤2 respawns, then escalate. - Read the plan; verify part sizing (no test-only parts) and that part contexts reference real files/symbols (spot-check). Record in the run record.
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.
- 4d ago First seen · 38 lines · 30 tokens per session scan A 5e0dcf4d3720
planning is a skill published in the GitHub repository scolladon/craft (2 stars, last pushed 16d ago), licensed MIT. It adds 30 tokens to every session and 534 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
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
implement-plan
Implement approved technical plans from thoughts/shared/plans/. ALWAYS use when the user says 'implement the plan', 'start implementing', 'build from the plan', or wants to execute a previously created implementation plan using TDD (Red-Green-Refactor). Supports team mode for parallel implementation.
nw-property-based-testing
Property-based testing strategies, mutation testing, shrinking, and combined PBT+mutation workflow for test quality validation.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…