Borrowing it
Nothing to install: this file belongs to knitli/codeweaver. 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/knitli/codeweaver/main/.claude/commands/plan.mdgit clone --depth 1 https://github.com/knitli/codeweaverWrote 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/knitli/codeweaver/plan)<a href="https://agentmods.dev/commands/knitli/codeweaver/plan"><img src="https://agentmods.dev/badge/commands/knitli/codeweaver/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/commands/knitli/codeweaver/plan"><img src="https://agentmods.dev/badge/commands/knitli/codeweaver/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.00000 | $0.00555 |
| Opus 5.5 | $0.00000 | $0.00222 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
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.
This is a copy
88% identical to plan — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description: Execute the implementation planning workflow using the plan template to generate design artifacts.
The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).
User input:
$ARGUMENTS
Given the implementation details provided as an argument, do this:
-
Run
.specify/scripts/bash/setup-plan.sh --jsonfrom the repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. All future file paths must be absolute.- BEFORE proceeding, inspect FEATURE_SPEC for a
## Clarificationssection with at least oneSessionsubheading. If missing or clearly ambiguous areas remain (vague adjectives, unresolved critical choices), PAUSE and instruct the user to run/clarifyfirst to reduce rework. Only continue if: (a) Clarifications exist OR (b) an explicit user override is provided (e.g., "proceed without clarification"). Do not attempt to fabricate clarifications yourself.
- BEFORE proceeding, inspect FEATURE_SPEC for a
-
Read and analyze the feature specification to understand:
- The feature requirements and user stories
- Functional and non-functional requirements
- Success criteria and acceptance criteria
- Any technical constraints or dependencies mentioned
-
Read the constitution at
.specify/memory/constitution.md(path relative to repo root) to understand constitutional requirements. -
Execute the implementation plan template:
- Load
.specify/templates/plan-template.md(already copied to IMPL_PLAN path) - Set Input path to FEATURE_SPEC
- Run the Execution Flow (main) function steps 1-9
- The template is self-contained and executable
- Follow error handling and gate checks as specified
- Let the template guide artifact generation in $SPECS_DIR:
- Phase 0 generates research.md
- Phase 1 generates data-model.md, contracts/, quickstart.md
- Phase 2 generates tasks.md
- Incorporate user-provided details from arguments into Technical Context: $ARGUMENTS
- Update Progress Tracking as you complete each phase
- Load
-
Verify execution completed:
- Check Progress Tracking shows all phases complete
- Ensure all required artifacts were generated
- Confirm no ERROR states in execution
-
Report results with branch name, file paths, and generated artifacts.
Use absolute paths with the repository root for all file operations to avoid path issues.
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 · 51 lines · 0 tokens per session scan A 14dcb02bef87
plan is a command published in the GitHub repository knitli/codeweaver (12 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 555 tokens. A static security scan graded it A with 0 findings. It is 88% identical to plan, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.