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-ideatenpx skills add EveryInc/compound-engineering-plugin --skill ce-ideategit 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.00055 | $0.01601 |
| Opus 5 | $0.00028 | $0.00800 |
| Sonnet 5 | $0.00011 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
ce-ideate 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Improvement Ideas
The current year is 2026 — use it when dating documents and checking recent artifacts.
ce-ideate runs before ce-brainstorm. This skill answers "which ideas are worth exploring?" ce-brainstorm then answers what one chosen idea should mean. ce-plan answers how it gets built.
Done: a ranked ideation artifact is written to <root>/ideation/ when that root is present, else to a CE temp path. Every idea generated has been critiqued, and the survivors are explained. The user is left holding the next-steps menu. No requirements, plans, or code.
Boundaries
- Ground before ideating. No advice detached from the repo.
- Generate many, critique all, explain survivors only. Generate the full candidate list before critiquing any of it. Rejection is explicit and carries a reason; this is not optimistic ranking.
- Route action into brainstorming. Never skip from ideation output to planning.
- Never dispatch on an unidentified subject. Ask instead, through the host's blocking question tool already in the current tool list (match by capability, not by a host-specific name). Presence in the current tool list is proof the tool exists; never call a user-facing question tool to discover whether it exists. If a matching tool is listed but unloaded, use the host's tool-discovery primitive to load that capability — do not search for another host's tool name. Where no such tool is in the list, offer numbered options on the user-visible surface. Never skip a question silently. Keep "Surprise me" a real option, alongside a Cancel that exits cleanly. Do not ask about solution direction, constraints, audience, tone, or success criteria —
ce-brainstormowns those. If it takes more than 3 questions, ideation is the wrong workflow. - Never print the internal taxonomy label. The labels
repo-grounded,elsewhere-software, andelsewhere-non-softwareroute dispatch only. Describe the mode to the user in the topic's own words. - Warn and proceed when grounding fails.
- Surface the cost line before dispatching.
What ships with it
17 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/issue-intelligence-analyst.md 15 KB
- references/agents/learnings-researcher.md 16 KB
- references/agents/slack-researcher.md 10 KB
- references/agents/web-researcher.md 8.9 KB
- references/decomposition.md 4.9 KB
- references/divergent-ideation.md 18 KB
- references/grounding.md 16 KB
- references/html-rendering.md 34 KB
- references/ideation-sections.md 8.5 KB
- references/issue-intelligence.md 4.7 KB
- references/markdown-rendering.md 11 KB
- references/output-mode.md 5.7 KB
- references/post-ideation-workflow.md 20 KB
- references/scope-gates.md 18 KB
- references/universal-ideation.md 19 KB
- references/user-research-artifacts.md 3.9 KB
- references/web-research-cache.md 4.1 KB
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 · 74 lines · 55 tokens per session scan A 896313cc31b0
ce-ideate is a skill published in the GitHub repository EveryInc/compound-engineering-plugin (24,760 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,601 once invoked, about $0.0003 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
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.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
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-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.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.