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/zeikar/hyperclaude/codex-changelognpx skills add zeikar/hyperclaude --skill codex-changeloggit clone --depth 1 https://github.com/zeikar/hyperclaudeWrote 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/zeikar/hyperclaude/codex-changelog)<a href="https://agentmods.dev/skills/zeikar/hyperclaude/codex-changelog"><img src="https://agentmods.dev/badge/skills/zeikar/hyperclaude/codex-changelog.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.1 | $0.00129 | $0.01838 |
| Opus 5 | $0.00064 | $0.00919 |
| Sonnet 5 | $0.00026 | $0.00368 |
| Haiku 4.5 | $0.00013 | $0.00184 |
Grade A, and why
codex-changelog 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codex-changelog — Codex CLI release watch (hyperclaude bridge relevance)
Repo-local dev tool (NOT a plugin skill). Compare a stored "last-checked" codex-cli STABLE version against the latest stable release, mine the release notes in between, and report only what touches this repo's Codex bridge — then optionally advance the stored version so the next run diffs from here.
The value is not "summarize Codex releases" — it is mapping generic Codex CLI changes onto the specific surface of the hyperclaude bridge (the only Codex-spawning code in the plugin) and verifying impact against the real bridge files.
Source (differs from cc-changelog)
Codex's CHANGELOG.md only points at GitHub Releases — it is NOT a per-version file.
So the authoritative source is the GitHub Releases of openai/codex, read via gh
(already authed in this repo):
gh release list --repo openai/codex --limit <N>— tags look likerust-v0.142.5(stable) andrust-v0.143.0-alpha.NN(pre-release). The row markedLatestis the current stable.gh release view <tag> --repo openai/codex— the per-release notes.
Step 2's get-releases.mjs helper wraps both calls (list → filter to new stables →
per-new-stable view), so you don't invoke gh by hand in the normal path.
Fallback if gh is unavailable: WebFetch https://github.com/openai/codex/releases.
Track STABLE, note alphas. The plugin runs against the installed stable codex, so
the version diff gates on stable→stable. The alpha stream (-alpha.NN, many per week)
is NOT tracked per-release — but DO surface a one-line "N newer alphas exist (latest
rust-v0.143.0-alpha.NN)" so upcoming changes are visible without firehose noise.
State file
.claude/skills/codex-changelog/.last-checked-version (sibling of this file,
gitignored): a single line with the last-reviewed codex-cli STABLE version, e.g.
0.142.5. It is the diff baseline; it advances only in Step 6.
Procedure
Step 1 — Baseline
The diff baseline is .claude/skills/codex-changelog/.last-checked-version (one stable
X.Y.Z line) — call it STORED. Step 2's helper reads it automatically; you don't Read
it here. If it's missing/empty the helper exits 2 — then ask which stable version to
baseline (or read the installed one via codex --version) and pass it as the argument.
What ships with it
2 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.
- 5d ago First seen · 118 lines · 129 tokens per session scan A f02bc9b17777
codex-changelog is a skill published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed yesterday), licensed MIT. It adds 129 tokens to every session and 1,838 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-31.
Other skills, from other repositories
pwp-deploy
Deployment protocol — safe, observable, reversible releases from main to production. Use this skill whenever the user is deploying, releasing, shipping, or pushing to production. Also use when they say 'deploy this', 'ship it', 'push to production', 'release', 'go live', 'pre-deploy check', 'rollback', 'feature…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
clean-user-facing-text
Audit and finalize authorized natural-language text meant for readers: strip suspicious invisible Unicode, then rewrite prose while keeping facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product copy, UI…
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
generate-tests
Generate unit tests for a .NET service following the coverage-kit conventions. Use when the user asks to 'generate tests', 'backfill tests', 'characterize this service', or 'add tests for' a target after coverage-init has run. Operates in characterization mode (freeze current behavior for existing code) or spec mode…