Borrowing it
Nothing to install: this file belongs to fulminate-io/knowledge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fulminate-io/knowledge-mcp/main/.claude/skills/plan-structure/SKILL.mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/plan-structure)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/plan-structure"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/plan-structure/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/fulminate-io/knowledge-mcp/plan-structure"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/plan-structure.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.00051 | $0.01489 |
| Opus 5.5 | $0.00020 | $0.00596 |
| Sonnet 5.5 | $0.00010 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
plan-structure 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLAN-STRUCTURE — phases, lifecycle, perf, and the shape of a plan
Phases survive context boundaries
Assume every phase is executed by a different implementer who never read the others. Every cross-phase dependency is a LOCKED NAME (identifiers named at plan time, repeated in creating AND consuming phases, matching exactly) or a WRITTEN ARTIFACT (measurements, census outputs, red-first raw output — named, with a completeness criterion; a phase whose predecessor's artifact is missing STOPS). Prose-only prerequisites are can-kicking — hoist into steps with criteria. Phases with disjoint FILES are not independent if their completion GATES span each other's surfaces. Red-first degrades to red-NEVER across a boundary unless the raw red output is a handoff artifact.
Phases are not commit units
A phase is a work-and-review unit; the ticket's changeset lands as ONE commit at completion. Never prescribe per-phase commits. Express ordering safety as WORKING-TREE invariants: when an intermediate tree state between phases is hazardous, name the hazardous state, add an always-on invariant-guard test red in exactly that state, forbid real operations against a tree in it. For each phase boundary, enumerate what running the system at that boundary's tree state would do — final-state-only reasoning hides the worst hazards.
Reproduction before regression
A defect-fixing step specifies a REPRODUCTION run RED FIRST against the unfixed tree (naming the expected failure message, so a setup error is distinguishable) and a REGRESSION that lives in the suite; state whether they are one test or two. A reproduction that would also pass with the mechanism absent proves nothing: asserting a control is CONFIGURED rather than that it ACTS; a validator rejecting when nothing issues the good input; waiting on a signal nothing raises; a fixture deriving two distinct values from one field. The reproduction must COMPILE against the unfixed tree (raw literals over not-yet-existing constants); label honestly which assertions start red vs which are CHARACTERIZATION GUARDS — claiming a guard as red-first is a false statement nobody re-runs the before-state to catch.
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 · 119 lines · 51 tokens per session scan A 50c00f10f2a2
plan-structure is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,489 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.