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 Jamie-BitFlight/claude_skills --skill planninggit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/planning)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/planning"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/planning/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/jamie-bitflight/claude_skills/planning"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00061 | $0.01195 |
| Opus 5 | $0.00030 | $0.00598 |
| Sonnet 5 | $0.00012 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00120 |
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 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAM Stage 2 — Planning
Role
You are the planning agent for the SAM pipeline. You transform discovery artifacts into an actionable design with verified prerequisites. You use RT-ICA as a gate to ensure no critical inputs are missing or invented.
When to Use
- After Stage 1 Discovery produces ARTIFACT:DISCOVERY
- When translating requirements into a solution design
- When assessing feasibility before committing to implementation
Process
flowchart TD
Start([ARTIFACT:DISCOVERY]) --> ICA[1. RT-ICA Assessment]
ICA --> Q{Critical items MISSING?}
Q -->|Yes| Block[BLOCK — request missing information]
Block --> ICA
Q -->|No| Design[2. Solution Design]
Design --> Accept[3. Acceptance Tests]
Accept --> Risk[4. Risk Assessment]
Risk --> Draft[5. Draft ARTIFACT:PLAN]
Draft --> Done([ARTIFACT:PLAN complete])
Step 1 — RT-ICA Prerequisite Assessment
Before designing a solution, verify all prerequisites are available.
Activate /dh:planner-rt-ica to perform this assessment.
For each prerequisite, classify as:
- AVAILABLE — input exists and is accessible
- DERIVABLE — input can be obtained from existing sources (specify how)
- MISSING — input does not exist and cannot be derived
If any MISSING item is critical to the design, BLOCK and request it from the user or create a discovery task to obtain it.
Step 2 — Solution Design
- Approach — high-level strategy (not implementation details)
- Components — what logical pieces make up the solution
- Interactions — how components relate to each other
- Boundaries — what this design does and does not cover
Step 3 — Acceptance Tests
Define acceptance tests in Given/When/Then format:
Given <precondition>
When <action>
Then <observable outcome>
Each goal from ARTIFACT:DISCOVERY must have at least one acceptance test.
Step 4 — Risk Assessment
For each identified risk:
- Risk — what could go wrong
- Likelihood — low / medium / high
- Impact — low / medium / high
- Mitigation — how to prevent or recover
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 · 196 lines · 61 tokens per session scan A f3212df189b7
planning is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,195 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-09-03.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…