Compound Engineering is a plugin that organizes software work into brainstorming, planning, implementation, review, and recording lessons for future changes. It is used with AI coding agents including Claude Code, Cursor, and Codex, and the catalogue entries provide parts of its agent, skill, command, and hook workflow.
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 skills add EveryInc/compound-engineering-plugin --skill ce-commit-push-prgit clone --depth 1 https://github.com/EveryInc/compound-engineering-pluginWrote 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/skills/everyinc/compound-engineering-plugin/ce-commit-push-pr)<a href="https://agentmods.dev/skills/everyinc/compound-engineering-plugin/ce-commit-push-pr"><img src="https://agentmods.dev/badge/skills/everyinc/compound-engineering-plugin/ce-commit-push-pr/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/skills/everyinc/compound-engineering-plugin/ce-commit-push-pr"><img src="https://agentmods.dev/badge/skills/everyinc/compound-engineering-plugin/ce-commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00042 | $0.01790 |
| Opus 5.5 | $0.00017 | $0.00716 |
| Sonnet 5.5 | $0.00008 | $0.00358 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
ce-commit-push-pr 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit, Push, and PR
Asking the user: use 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. Fall back to asking in chat only when no such tool is in the list or a real question call errors, and never silently skip the question.
Mode
- Description-only — the user wants just a description ("write/draft a PR description", "describe this PR", a pasted PR URL or number). Run Step 4 only and print it. Apply it only if asked. Pass any pasted PR ref so Pre-A resolves the range.
- Description update — refresh or rewrite an existing PR's description, with no commit or push intent. Resolve PR presence by the Context rule below: an exit-0
[]is "no open PR" (report it and stop), and a non-zero exit is unknown (resolve auth or connectivity, then stop until presence is known). With an open PR, run Step 4 in PR mode on that URL, then Step 5 to preview, confirm, and apply viagh pr edit. - Full workflow — otherwise: Steps 1-5. Enter Stack mode instead when intent or preference wants a stack.
mode:pipeline modifier, set by orchestrated callers such as lfg. Run the resolved mode non-interactively and suppress every blocking ask. Each suppressed ask takes the conservative default: no existing-PR rewrite, the branch kept, an unresolvable base stopping rather than guessed, and a description-update preview applied directly, since that invocation is the apply intent. Pipeline stack mode uses only the intent and scope on the invocation and passes posture into the handoff.
Stack mode (opt-in)
Opt-in only. Enter it when intent or standing preference wants a multi-PR stack. An explicit stack request is required intent — do not re-read it as a single PR with a custom --base. Do not proactively suggest PR stacks. When the user did not ask for one, refuse nonsense stacks (one logical change, artificial slices) and stay single-PR.
What ships with it
9 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/apply-and-handoff.md 13 KB
- references/branch-creation.md 1.8 KB
- references/commit-and-push.md 3.0 KB
- references/compose.md 4.8 KB
- references/context.md 5.7 KB
- references/gh-stack-cli.md 3.8 KB
- references/pr-description-writing.md 25 KB
- references/stack-submit.md 12 KB
- references/visual-evidence.md 5.6 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 Changed cfff5c36885f
- 4d ago Changed f235abd646f9
- 5d ago Changed · -10 lines 51f1a5c39bbd
- 1mo ago Changed deb35ce03204
- 1mo ago Changed e4c197072adc
- 2mo ago Changed · +2 lines d4098d9b0a95
- 2mo ago First seen · 68 lines · 42 tokens per session scan A f9453c4c3f78
ce-commit-push-pr is a skill published in the GitHub repository EveryInc/compound-engineering-plugin (25,945 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,790 once invoked, about $0.0002 per session on Opus 5.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.
ce-commit-push-pr compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ce-commit-push-prEveryInc/compound-engineering-plugin | Skill | 26k | yesterday | MIT | A | 42 | Claude Code |
| atlas-changelogtonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 45 | Claude Code |
| apex-statustonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 42 | Claude Code |
| repo-shipaethrox/doctrine | Skill | 19 | 1mo ago | MIT | A | 68 | Claude Code, Codex |
| superpowers-requesting-code-reviewregen-coordination/org-os-template | Skill | 5 | yesterday | MIT | A | 25 | Claude Code, Codex |
| git-commitThinkInAIXYZ/deepchat | Skill | 6.4k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| engineer-bot-opsmakecindy/cindy | Skill | 9.3k | yesterday | Apache-2.0 | A | 57 | Claude Code, Codex |