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 agentmods add skills/everyinc/compound-engineering-plugin/ce-plannpx skills add EveryInc/compound-engineering-plugin --skill ce-plangit clone --depth 1 https://github.com/EveryInc/compound-engineering-pluginWhat 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 | $0.00048 | $0.01679 |
| Opus 5 | $0.00024 | $0.00839 |
| Sonnet 5 | $0.00010 | $0.00336 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
ce-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 2d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Technical Plan
Note: The current year is 2026.
Outcome: a plan an implementer can start from confidently — a few sentences in chat, a chat brief, or a durable plan artifact — handed off through its owning terminal workflow. ce-brainstorm defines WHAT to build as a requirements-only unified plan; ce-plan enriches it with HOW; ce-work executes it. A prior brainstorm is useful but never required.
An explicit invocation always produces a plan. Never classify a direct invocation as "not a planning task" and route out. It may select any output contract below, and the smallest valid plan is a few sentences in chat.
Research, decide, and write the plan — never implement. Do not write production code, run tests, or learn from execution-time results. Directional pseudo-code and grammar sketches may communicate design; changing code to see what happens belongs in ce-work.
Mandatory Completion Contract
A run is complete when its output contract's done condition is met. Every normal interactive branch that produces a plan artifact or checkpoint is incomplete until its owning handoff question is presented: for a Durable software implementation-plan run that continues past Phase 0.1b, the Phase 5.4 menu presented and any selected action has actually fired. For Direct, the change stated and the handoff offered; for a Chat brief, the brief and its one-line save-or-ce-work offer in chat. Neither presents the Phase 5.4 menu. Non-software and approach-altitude routes use their reference workflow's terminal handoff. Answer-seeking may end after the answer unless its owner requires save/share.
Writing the file, checking confidence, and running or explicitly skipping ce-doc-review are intermediate milestones. Pipeline mode is complete only when the plan, confidence check, and non-interactive document-review state are returned to its caller; the caller owns the next action.
Interaction Method
Ask one question at a time through the host's blocking question tool already in the current tool list. Match by capability; never probe a user-facing tool to discover it. If none is listed or a real question call errors, render numbered choices in chat; never silently skip a required question. If no feature description was supplied, ask what to plan and wait.
What ships with it
35 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/agents/agent-native-planning-strategist.md 4.0 KB
- references/agents/architecture-strategist.md 3.2 KB
- references/agents/best-practices-researcher.md 7.0 KB
- references/agents/data-integrity-guardian.md 3.2 KB
- references/agents/data-migration-reviewer.md 5.7 KB
- references/agents/deployment-verification-agent.md 5.0 KB
- references/agents/framework-docs-researcher.md 5.5 KB
- references/agents/git-history-analyzer.md 2.8 KB
- references/agents/learnings-researcher.md 16 KB
- references/agents/pattern-recognition-specialist.md 3.6 KB
- references/agents/performance-oracle.md 4.5 KB
- references/agents/repo-research-analyst.md 15 KB
- references/agents/security-sentinel.md 4.0 KB
- references/agents/slack-researcher.md 10 KB
- references/agents/spec-flow-analyzer.md 4.7 KB
- references/agents/web-researcher.md 8.9 KB
- references/approach-altitude.md 7.4 KB
- references/deepening-workflow.md 20 KB
- references/final-review.md 18 KB
- references/html-rendering.md 34 KB
- references/intake.md 19 KB
- references/markdown-rendering.md 11 KB
- references/output-contracts.md 2.9 KB
- references/output-mode.md 7.2 KB
- references/plan-handoff.md 25 KB
- references/plan-sections.md 30 KB
- references/reasoning-elevation.md 17 KB
- references/research.md 18 KB
- references/resume.md 9.3 KB
- references/settled-decisions.md 4.8 KB
- references/structure.md 18 KB
- references/synthesis-summary.md 43 KB
- references/universal-planning.md 15 KB
- scripts/elevation-dispatch.sh 13 KB runs code
- scripts/peer-job-runner.py 99 KB runs code
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.
- 2d ago First seen · 61 lines · 48 tokens per session scan A 903a355be1d9
ce-plan is a skill published in the GitHub repository EveryInc/compound-engineering-plugin (24,760 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,679 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.