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/jerrylalala/compound-engineering/ce-updatenpx skills add Jerrylalala/compound-engineering --skill ce-updategit clone --depth 1 https://github.com/Jerrylalala/compound-engineeringWrote 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/jerrylalala/compound-engineering/ce-update)<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/ce-update"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/ce-update.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.00999 |
| Opus 5 | $0.00031 | $0.00500 |
| Sonnet 5 | $0.00012 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
ce:update scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
access, `gh`, `curl`, Python, or Node may be unavailable) and stop. How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Plugin Version
Verify the installed compound-engineering plugin version matches the public
repository plugin.json on main, and recommend the update command if it
doesn't. Claude Code only.
The public repository version comes from
plugins/compound-engineering/.claude-plugin/plugin.json on main rather than
the latest GitHub release tag, because the marketplace installs plugin contents
from main HEAD. Comparing against release tags
false-positives whenever main is ahead of the last tag (the normal state
between releases).
Step 1: Probe versions
Run these three scripts in parallel via the Bash tool. Each prints a single
line of output; capture the values for the decision logic below. Use
${CLAUDE_SKILL_DIR} so the path resolves correctly in both claude --plugin-dir
local-development sessions and standard marketplace-cached installs.
bash "${CLAUDE_SKILL_DIR}/scripts/upstream-version.sh"
bash "${CLAUDE_SKILL_DIR}/scripts/currently-loaded-version.sh"
bash "${CLAUDE_SKILL_DIR}/scripts/marketplace-name.sh"
scripts/upstream-version.sh reads plugin.json on main via gh api, then
falls back to the GitHub Contents API when gh is unavailable in the shell
PATH. It avoids raw.githubusercontent.com because the raw CDN can briefly serve
stale content immediately after release automation updates main. It prints
the version string, or the sentinel __CE_UPDATE_VERSION_FAILED__ if the
public repository version cannot be fetched or parsed.
scripts/currently-loaded-version.sh and scripts/marketplace-name.sh parse
${CLAUDE_SKILL_DIR} against the marketplace-cache layout
~/.claude/plugins/cache/<marketplace>/compound-engineering/<version>/skills/ce-update.
They print the version segment / marketplace segment, or the sentinel
__CE_UPDATE_NOT_MARKETPLACE__ if the path doesn't match (typical for
claude --plugin-dir local development).
Step 2: Apply decision logic
Handle failure cases
If scripts/upstream-version.sh printed __CE_UPDATE_VERSION_FAILED__: tell
the user the public repository version could not be fetched or parsed (network
access, gh, curl, Python, or Node may be unavailable) and stop.
What ships with it
3 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.
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.
- 4d ago First seen · 97 lines · 62 tokens per session scan A 318c3db6c722
ce:update is a skill published in the GitHub repository Jerrylalala/compound-engineering (5 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 999 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…