Borrowing it
Nothing to install: this file belongs to BostonOrange/claude-code-framework. 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/BostonOrange/claude-code-framework/main/.claude/skills/ccf-change-control/SKILL.mdgit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/ccf-change-control)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-change-control"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-change-control/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/bostonorange/claude-code-framework/ccf-change-control"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-change-control.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.00114 | $0.03043 |
| Opus 5.5 | $0.00046 | $0.01217 |
| Sonnet 5.5 | $0.00023 | $0.00609 |
| Haiku 4.5 | $0.00011 | $0.00304 |
Grade B, and why
ccf-change-control scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Rule-id stability rule: `grep -n 'stable forever' .claude/rules/templates.md` How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCF Change Control
How a change to this framework is classified, gated, reviewed, and landed. The core model: deterministic tests are the hard gate; agents are advisory layers on top of it. No agent opinion, review, or skill instruction may route around a failing tests/run-all.sh.
Usage
Load this skill when you are about to change framework files and need to know what must happen before the change counts as done — or when you see a failing check and need to know whether to fix the change or the check.
Do NOT use this skill for:
- WHICH count/table lives in WHICH file — that matrix is owned by ccf-doc-sync-campaign
- HOW to mirror setup.sh into setup.ps1 — ccf-parity-playbook
- Internals of each
tests/check-*.shscript — ccf-testing-and-qa - Mechanics of
.claude/vstemplates/and the drift allowlist format — ccf-dogfood-and-drift
Process
1. Classify the change
| Class | Examples | Minimum gate | Extra obligations |
|---|---|---|---|
| doc-only | README wording, docs/ guides | bash tests/run-all.sh (counts/tables are still parsed) |
None if no counts touched |
| template-content | new/edited file in templates/agents|commands|rules|hooks/, skills/ |
full suite; check-templates.sh, check-placeholders.sh, check-consistency.sh, check-agent-registry.sh, check-dogfood-drift.sh all bite |
Update every doc surface + config/agents.json for agents (see ccf-doc-sync-campaign); sync or allowlist the .claude/ twin |
| setup-script | setup.sh / setup.ps1 |
full suite incl. check-setup-smoke.sh; PowerShell smoke (see phase 3 warning) |
Mirror in the other script in the SAME change (.claude/rules/setup-scripts.md) |
| test | tests/check-*.sh, tests/check-setup-smoke.ps1 |
full suite; new check-*.sh files are auto-discovered by run-all.sh (find pattern) |
State what the test newly gates in the commit message |
| config-schema | config/*.json |
full suite; check-agent-registry.sh locksteps config/agents.json with templates/agents/*.md, README.md, templates/CLAUDE.md.template, docs/teams.md, docs/agents-commands-rules.md |
Treat keys as an interface consumed by setup scripts |
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 · 127 lines · 114 tokens per session scan B 0e7a3294b37e
ccf-change-control is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 114 tokens to every session and 3,043 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.