Borrowing it
Nothing to install: this file belongs to BenchBox-dev/BenchBox. 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/BenchBox-dev/BenchBox/develop/.claude/skills/shared-change-framework/SKILL.mdgit clone --depth 1 https://github.com/BenchBox-dev/BenchBoxWrote 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/benchbox-dev/benchbox/shared-change-framework)<a href="https://agentmods.dev/skills/benchbox-dev/benchbox/shared-change-framework"><img src="https://agentmods.dev/badge/skills/benchbox-dev/benchbox/shared-change-framework/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/benchbox-dev/benchbox/shared-change-framework"><img src="https://agentmods.dev/badge/skills/benchbox-dev/benchbox/shared-change-framework.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.00034 | $0.01683 |
| Opus 5.5 | $0.00014 | $0.00673 |
| Sonnet 5.5 | $0.00007 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
change-framework 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 26d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Framework
1. Source-code selection
After required research and before editing source code, choose the first option that fully satisfies the authorized requirement, repository policy, and safety constraints:
- No change, if the required outcome already exists.
- An existing helper or established pattern.
- A standard-library or native platform feature.
- A declared, direct dependency supported by the project.
- The smallest clear new implementation.
Do not trade correctness, compatibility, validation, security, accessibility, or explicit requirements for an earlier option. When a simplification has a material or non-obvious limit, document the limit and its replacement trigger.
2. Slicing discipline
Use for multi-file work, features, refactors, or changes likely to exceed about 100 lines before testing.
- Touch only task-required code. Report adjacent issues as "noticed but not touching."
- Prefer vertical slices. Use contract-first slices for parallel components and risk-first slices for uncertainty.
- Each slice must implement, test, and verify one logical behavior. Commit each verified slice separately.
- Keep the project buildable and each increment independently revertible.
- New incomplete code stays disabled by default.
3. Post-edit verification ladder
Run before returning, staging, or committing changes.
Checks
- Read edited regions with five surrounding lines. Check indentation, nesting, stale imports, and orphaned lines.
- Run project lint if available.
- Run project typecheck if available.
- Run targeted tests, then fast/default suite for meaningful code changes.
Rules
- Report why any verification step is unavailable.
- Fix failures before committing or report the blocker.
- Report command, result, and residual risk.
- Run the narrowest proving check first. Use fast, full, or preflight checks as final gates. Save long output to a log and report the summary.
Delegated gate runs
A low-effort subagent may run deterministic gates, including full tests, preflight, CI status, push, PR opening or follow-up, and other long run-and-report commands.
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.
- 26d ago Changed · +1 lines d795e905c473
- 1mo ago First seen · 161 lines · 34 tokens per session scan A 952459319240
change-framework is a skill published in the GitHub repository BenchBox-dev/BenchBox (12 stars, last pushed 21d ago), licensed MIT. It adds 34 tokens to every session and 1,683 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-09-04.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…