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-brainstormnpx skills add EveryInc/compound-engineering-plugin --skill ce-brainstormgit 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.00112 | $0.01723 |
| Opus 5 | $0.00056 | $0.00861 |
| Sonnet 5 | $0.00022 | $0.00345 |
| Haiku 4.5 | $0.00011 | $0.00172 |
Grade A, and why
ce-brainstorm 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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm a Feature or Improvement
Brainstorming answers WHAT to build through dialogue; ce-plan then enriches the same unified plan artifact with HOW. This skill does not implement code. The current year is 2026, for dating the artifact.
Outcome: a right-sized result planning can enrich without inventing product behavior, scope boundaries, or success criteria: a chat paragraph for Lightweight work, or a requirements-only unified plan under <root>/plans/ when a file is earned.
Done, on the brainstorm path: that artifact is written and passes the Ready for Planning Check — or no file was written because the dialogue produced no decision a downstream consumer needs in IDed form and the user asked for none — and Phase 4's handoff has been presented.
Lightweight work ends in chat. Phase 0.3 classifies the tier from the request and bounded inline reads before anything is dispatched; when the tier is uncertain, take the heavier one. Lightweight work — small, well-bounded, low ambiguity — ends in a chat paragraph with no file, no grounding scout, no approach generation, and no claim verifier. A file is earned only by a decision a downstream consumer needs in IDed form, or by the user asking for one.
Stop and route instead in three cases, decided by references/phase-0.md, not from memory. Each ends the run its own way, so the done bar above does not apply: non-software work, where references/universal-brainstorming.md replaces Phases 0.2–4; a verdict question about a named external candidate, where you offer the ce-pov handoff; and neither — quick help, a factual question, a single-step task — answered directly.
The feature description is what the invocation carries, whether the user wrote it or a calling skill passed it. If none came, ask the user what they want to explore and do not proceed until you have one.
Artifact Root
Resolve <root> the first time you compose or read a <root>/ path, never earlier; a scratch-only or no-repo run that touches none skips this entirely.
What ships with it
23 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/slack-researcher.md 10 KB
- references/approaches.md 7.1 KB
- references/blindspot-pass.md 7.4 KB
- references/brainstorm-sections.md 25 KB
- references/dialogue.md 12 KB
- references/handoff.md 12 KB
- references/html-rendering.md 34 KB
- references/interaction-rules.md 6.4 KB
- references/markdown-rendering.md 11 KB
- references/model-tiers.md 1.7 KB
- references/output-mode.md 4.9 KB
- references/phase-0.md 14 KB
- references/plan-write.md 4.5 KB
- references/product-pressure-test.md 3.5 KB
- references/reasoning-elevation.md 17 KB
- references/settled-decisions.md 4.8 KB
- references/synthesis-summary.md 28 KB
- references/universal-brainstorming.md 7.6 KB
- references/verdict-routing.md 4.2 KB
- references/visual-probes.md 12 KB
- scripts/elevation-dispatch.sh 13 KB runs code
- scripts/light-webserver.js 14 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.
- 3d ago First seen · 68 lines · 112 tokens per session scan A 5ffe0af9c8fd
ce-brainstorm is a skill published in the GitHub repository EveryInc/compound-engineering-plugin (24,760 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 1,723 once invoked, about $0.0006 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-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
spec-to-tickets
Turns an already-discussed plan into a written spec and a set of tracer-bullet tickets, synthesizing rather than re-interviewing, slicing work end-to-end rather than by layer, and gating entry/exit with a written Definition of Ready and Definition of Done rather than by feel. Use when the user asks to turn a…
handoff
Hand off in-progress work, an on-call shift, or an open incident to another person or agent using a fixed four-part structure, so nothing load-bearing is lost between one owner and the next. Use when work needs to change hands mid-flight, an on-call rotation is ending, or a session needs to brief whoever picks this up…
triage
Classify and prioritize an incoming bug report or feature request using Impact × Urgency, and route it to the right next step. Use when the user wants a backlog triaged, an issue prioritized, or asks whether something is worth working on now versus later.