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 BostonOrange/claude-code-framework --skill plangit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/plan)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/plan"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/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/bostonorange/claude-code-framework/plan"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/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.00063 | $0.00958 |
| Opus 5.5 | $0.00025 | $0.00383 |
| Sonnet 5.5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Multi-Agent Planning
A specialist-driven plan for the current branch's work. The planner-coordinator agent classifies scope, spawns the right planning specialists in parallel, and synthesizes their outputs into a single plan document.
Usage
/plan — plan the current task using conversation context
/plan TICKET-123 — plan a tracked ticket; reads docs/stories/TICKET-123/story.md
/plan --refresh — re-run planning even if a plan exists for this branch
/plan --scope=large — override the auto-classified scope (forces all specialists)
Process
Phase 1: Read the Story
Source of the story:
- If a TICKET-id is passed, read
docs/stories/<TICKET-id>/story.md(and any linked design docs) - Otherwise, use the user's stated task from conversation context
- If neither is available, ask the user
Phase 2: Spawn the Planner Coordinator
Spawn planner-coordinator as a sub-agent:
Invoke planner-coordinator on the following story: <story>.
Use scope classifier to pick specialists.
Write the plan to .claude/state/plan-<branch>.md.
Surface blocking questions and the next action.
The coordinator handles:
- Scope classification (
tiny/small/medium/large) - Specialist selection
- Parallel spawning of Wave 1 (
requirements-clarifier,scope-decomposer,architect,api-designer,database-architect) - Sequential spawning of Wave 2 (
risk-assessor,test-strategy-planner— they consume Wave 1 outputs) - Merging into a single plan
- Persisting to
.claude/state/plan-<branch>.md
Phase 3: Surface to User
Show the user:
- Scope and specialist selection (so they know what was checked)
- Blocking questions (most important — work cannot start until resolved)
- The work-breakdown table (collapsed sub-steps unless asked)
- Top 3 risks
- Next action (resolve questions → re-plan, OR proceed to
/build)
Phase 4: Save and Exit
The plan file is the state. No additional persistence needed.
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.
- 1mo ago First seen · 96 lines · 63 tokens per session scan A 6b89b59c25a4
plan is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 958 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…