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 oborchers/fractional-cto --skill master-plan-methodologygit clone --depth 1 https://github.com/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/master-plan-methodology)<a href="https://agentmods.dev/skills/oborchers/fractional-cto/master-plan-methodology"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/master-plan-methodology/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/oborchers/fractional-cto/master-plan-methodology"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/master-plan-methodology.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.00270 | $0.05694 |
| Opus 5.5 | $0.00108 | $0.02278 |
| Sonnet 5.5 | $0.00054 | $0.01139 |
| Haiku 4.5 | $0.00027 | $0.00569 |
Grade A, and why
master-plan-methodology 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Master Plan Methodology
A master plan is a long, multi-phase planning document that decomposes a topic, ticket, or roadmap item into actionable phases. Each phase maps 1:1 to a Claude Code /plan-mode session. The master plan is the durable artifact; the per-phase plans in ~/.claude/plans/<slug>.md are ephemeral.
This skill codifies the format and conventions every master plan must follow. The plan-master-architect agent writes plans to this spec; the plan-verifier agent audits plans against it.
The 5-step workflow
The plugin orchestrates master plans through five steps:
/planning-tools:plan-context [topic | path] [--domains a,b,c]— Pre-load context. Stage 1 Triage decides domains, Stage 2 Announce prints them without asking, Stage 3 dispatches parallel Explore agents (one per domain), Stage 4 verifies findings with direct Reads. Emits a scope report. NO plan file written./planning-tools:plan-master [topic] [--context <report-path>]— Draft the master plan. Reuses a fresh/planning-tools:plan-contextreport if--contextis passed; otherwise runs the same Triage + Explore + Verify pre-flight internally. Then synthesizes the multi-phase plan via theplan-master-architectagent (opus). Writes to a project-local path./planning-tools:plan-verify <path>— Audit the drafted plan. Dispatches theplan-verifieragent against theplan-verification-checklistskill, presents Critical/Important/Suggestion findings, and (on user approval) appends a- **Verified:** YYYY-MM-DDbullet to the context block (a> **Verified:**line on legacy blockquote plans).- Manual phase iteration — User copies the next unticked phase into Claude Code's built-in
/plan. Plan mode produces the per-phase plan in~/.claude/plans/<slug>.md. User executes the phase and manually ticks the row in the master plan. /planning-tools:plan-delete— Clears the per-session plan file. Loop back to step 4 for the next phase.
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 · 324 lines · 270 tokens per session scan A 5e06232e62de
master-plan-methodology is a skill published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 270 tokens to every session and 5,694 once invoked, about $0.0011 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-10-13.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.