Borrowing it
Nothing to install: this file belongs to Consiliency/Code-Index-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/Consiliency/Code-Index-MCP/main/.claude/commands/plan-phase.mdgit clone --depth 1 https://github.com/Consiliency/Code-Index-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/commands/consiliency/code-index-mcp/plan-phase)<a href="https://agentmods.dev/commands/consiliency/code-index-mcp/plan-phase"><img src="https://agentmods.dev/badge/commands/consiliency/code-index-mcp/plan-phase/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/commands/consiliency/code-index-mcp/plan-phase"><img src="https://agentmods.dev/badge/commands/consiliency/code-index-mcp/plan-phase.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.00000 | $0.00658 |
| Opus 5.5 | $0.00000 | $0.00263 |
| Sonnet 5.5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
plan-phase 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 2mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Implementation For a Spec Phase (Architecture-First, Code-Boundary Swim Lanes)
Inputs:
$1= spec file path relative tospec/(e.g.,MASTER_ROADMAP.md,api/ocr-pipeline.md)$2= phase name or identifier within that spec (e.g.,Phase 2 – Ingestion Service)
The goal is to design the best architecture first, then define swim lanes that fit that architecture. Do not alter the design to accommodate swim lanes.
0. Load & Scope
- Read the spec file:
@spec/$1
- Find the phase whose heading/label best matches
"$2".- Treat this phase as the primary scope.
- Consider other phases only when explicitly referenced as dependencies.
A. Architectural Baseline & Component Catalog (For Phase $2)
From the requirements of phase $2, define the post-implementation component catalog:
-
Files
- Paths to be added, modified, or removed.
- Reuse existing files when it makes architectural sense.
-
Classes / Types
- Names, paths, visibility.
- Mark each as new or modified.
-
Functions / Methods
- Names, paths, signatures:
- Parameters (names, types, optionality).
- Return type.
- Error behavior.
- Names, paths, signatures:
-
Data Structures
- DTOs, event payloads, schemas, enums, config.
- Fields + types, required vs optional, invariants, versioning.
At this stage, do not assign swim lanes. Focus entirely on optimal phase-level architecture.
B. Code-Level Interface Contracts (Freeze Before Lane Work)
Define interfaces that span module or service boundaries for phase $2:
- Types of interfaces:
- HTTP/GraphQL/RPC endpoints (routes + handler symbols).
- Public library APIs (exported functions/methods).
- Events/queues/topics with payload schemas.
- DB queries/contracts and schema changes.
For each interface:
- Specify:
- Defining file(s) and symbol names.
- Input/output shapes (types, fields).
- Error behavior, including failure modes and retry semantics.
- Invariants and idempotency guarantees where relevant.
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.
- 2mo ago First seen · 87 lines · 0 tokens per session scan A e63884e72ab8
plan-phase is a command published in the GitHub repository Consiliency/Code-Index-MCP (60 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 658 tokens. 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-30.
plan-phase compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plan-phaseConsiliency/Code-Index-MCP | Command | 60 | yesterday | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |