Borrowing it
Nothing to install: this file belongs to deonmenezes/mantishack. 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/deonmenezes/mantishack/main/.codex/skills/code-review-breaking-changes/SKILL.mdgit clone --depth 1 https://github.com/deonmenezes/mantishackWrote 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/deonmenezes/mantishack/code-review-breaking-changes)<a href="https://agentmods.dev/skills/deonmenezes/mantishack/code-review-breaking-changes"><img src="https://agentmods.dev/badge/skills/deonmenezes/mantishack/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/deonmenezes/mantishack/code-review-breaking-changes"><img src="https://agentmods.dev/badge/skills/deonmenezes/mantishack/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 deonmenezes/mantishack (504 stars, last pushed 18d 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
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
C31-debug
Investigate bugs through reproduction → trace → hypothesis → test-first fix → verify → archive. All active sessions are tracked in memory/.planning/debug/ for resumption and knowledge compounding.
C31-research
Unified research skill. Covers best practices, framework documentation, git history, community issues, institutional memory, and bug reproduction. All modes are read-only — does not write code.
gsd-map-codebase
A codebase mapping tool that studies an existing software project and records its structure, technologies, coding conventions, and possible problem areas in Markdown files.
C31-workflow-bug-reproduction
Read-only workflow agent. Systematically reproduces bugs: hypothesize causes → construct minimal reproduction → verify. Use when a bug report is vague, when regression tests are missing, or when separating environment bugs from code bugs.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.