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-release-notesnpx skills add Jerrylalala/compound-engineering --skill ce-release-notesgit 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-release-notes)<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/ce-release-notes"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/ce-release-notes.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.00027 | $0.01884 |
| Opus 5 | $0.00014 | $0.00942 |
| Sonnet 5 | $0.00005 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
ce:release-notes 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 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.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compound-Engineering Release Notes
Look up what shipped in recent releases of the compound-engineering plugin. Bare invocation summarizes the last 5 plugin releases. Argument invocation searches the last 40 releases and answers a specific question, citing the release version that introduced the change.
Data comes from the GitHub Releases API for Jerrylalala/compound-engineering, filtered to the compound-engineering-v* tag prefix so sibling components (cli-v*, coding-tutor-v*, marketplace-v*, cursor-marketplace-v*) are excluded.
Phase 1 — Parse Arguments
Split the argument string on whitespace. Strip every token that starts with mode: — these are reserved flag tokens; v1 does not act on them but still strips them so a stray mode:foo is not treated as a query string. Join the remaining tokens with spaces and apply .strip() to the result.
- Empty result → summary mode (continue to Phase 2).
- Non-empty result → query mode (skip to Phase 5).
Version-like inputs (2.65.0, v2.65.0, compound-engineering-v2.65.0) are query strings, not a separate lookup-by-version mode. They flow through query mode like any other text.
Phase 2 — Fetch Releases (Summary Mode)
Run the helper from the skill directory:
python3 scripts/list-plugin-releases.py --limit 40
The helper always exits 0 and emits a single JSON object on stdout. It owns all transport logic (gh preferred, anonymous API fallback) — never branch on transport here.
If the helper subprocess itself fails to launch (non-zero exit AND empty or non-JSON stdout — e.g., python3 is not installed, the script is not executable, or the interpreter crashes before emitting the contract), tell the user:
python3is required to run/ce:release-notes. Install Python 3.x and retry, or open https://github.com/Jerrylalala/compound-engineering/releases directly.
Then stop. This is distinct from the helper returning ok: false, which means the helper ran successfully but both transports failed (handled below).
What ships with it
1 file 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 · 156 lines · 27 tokens per session scan A 69286736b46a
ce:release-notes is a skill published in the GitHub repository Jerrylalala/compound-engineering (5 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,884 once invoked, about $0.0001 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-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…