Borrowing it
Nothing to install: this file belongs to extracurricular-ai/codex-rewind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/extracurricular-ai/codex-rewind/main/.codex/skills/code-review-breaking-changes/SKILL.mdgit clone --depth 1 https://github.com/extracurricular-ai/codex-rewindWrote 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/extracurricular-ai/codex-rewind/code-review-breaking-changes)<a href="https://agentmods.dev/skills/extracurricular-ai/codex-rewind/code-review-breaking-changes"><img src="https://agentmods.dev/badge/skills/extracurricular-ai/codex-rewind/code-review-breaking-changes/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/extracurricular-ai/codex-rewind/code-review-breaking-changes"><img src="https://agentmods.dev/badge/skills/extracurricular-ai/codex-rewind/code-review-breaking-changes.svg" alt="Reviewed on agentmods" width="80" 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.00007 | $0.00062 |
| Opus 5.5 | $0.00003 | $0.00025 |
| Sonnet 5.5 | $0.00001 | $0.00012 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
code-breaking-changes 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 1mo 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.
This is a copy
100% identical to code-breaking-changes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Search for breaking changes in external integration surfaces:
- app-server APIs
- CLI parameters
- configuration loading
- resuming sessions from existing rollouts
Do not stop after finding one issue; analyze all possible ways breaking changes can happen.
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.
- 1mo ago First seen · 13 lines · 7 tokens per session scan A 9981e74df2e8
code-breaking-changes is a skill published in the GitHub repository extracurricular-ai/codex-rewind (56 stars, last pushed 28d ago), licensed Apache-2.0. It adds 7 tokens to every session and 62 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-breaking-changes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
gate-release
Comprehensive pre-release review combining code quality, security audit, and production readiness checks.
gate-code
Review code implementation for security vulnerabilities, code quality, testing, and adherence to design specifications.
gate-design
Review technical design documents for API contracts, data models, component architecture, and technology decisions.
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.