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 skills add berkcangumusisik/claude-code-practices --skill breaking-changesgit clone --depth 1 https://github.com/berkcangumusisik/claude-code-practicesWrote 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/berkcangumusisik/claude-code-practices/breaking-changes)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/breaking-changes"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/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/berkcangumusisik/claude-code-practices/breaking-changes"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/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.00017 | $0.00326 |
| Opus 5.5 | $0.00007 | $0.00130 |
| Sonnet 5.5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
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.
What it actually says
Breaking Change Detection
Base: $1 (e.g., v1.2.0, main)
Head: $2 (default: current HEAD)
- Get the diff:
git diff $1 ${2:-HEAD} -- src/ --name-only
git diff $1 ${2:-HEAD} -- src/
- Analyze changes for breakage:
Public API changes (exports):
- Removed exported functions/types
- Changed function signatures (added required params, changed types)
- Changed return types
Database changes:
- Removed columns (app code still references them?)
- Renamed columns/tables
- Changed column types
Config/env changes:
- Renamed environment variables
- New required env vars without defaults
Behavior changes:
- Changed default values
- Changed error types/messages (if consumers check these)
- For each breaking change, write a migration step:
## Breaking Changes in v2.0.0
### `createUser()` now requires `role` parameter
**Before:** `createUser({ name, email })`
**After:** `createUser({ name, email, role: 'user' })`
**Migration:** Add `role: 'user'` as default to all call sites.
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 · 50 lines · 17 tokens per session scan A dc8abc5cd575
breaking-changes is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (11 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 326 once invoked, about $0.0001 per session on Opus 5.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
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-drive-pr
PR mergeability, CI, and live preview.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
explain-pr
Explain a PR: the background problem and the proposed solution.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.