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-parity-playbook/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-parity-playbook)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-parity-playbook"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-parity-playbook/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-parity-playbook"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-parity-playbook.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.00117 | $0.03501 |
| Opus 5.5 | $0.00047 | $0.01400 |
| Sonnet 5.5 | $0.00023 | $0.00700 |
| Haiku 4.5 | $0.00012 | $0.00350 |
Grade B, and why
ccf-parity-playbook 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.
- Parity contract text: `cat .claude/rules/setup-scripts.md` How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCF Parity Playbook: setup.sh <-> setup.ps1 Mirror Discipline
Usage
Load this skill when you are about to change setup.sh or setup.ps1, review a diff that touches either, debug a Windows-only installer failure, or audit whether the two installers still match. Not for: what the setup scripts install, their flag semantics, and the CCF_* variable catalog (see ccf-release-and-install), or general test anatomy (see ccf-testing-and-qa). Doc-count drift is ccf-doc-sync-campaign's territory.
Core law (from .claude/rules/setup-scripts.md): the two installers MUST have feature parity — every prompt, placeholder mapping, copy operation, conditional, and summary line in one must exist in the other. There is no shared implementation; parity is maintained by hand and enforced only partially by tests, which is why this playbook exists.
Process: the parity walk for any setup change
- Make the change in
setup.shfirst. It is the reference implementation (1332 lines vs 1153 insetup.ps1, as of 2026-07-11) and the only one the local test suite executes. - Walk the parity checklist (next section) row by row and mirror each touched row into
setup.ps1. Match section numbering — both scripts use identical numbered prompt sections1. Project Typethrough7. Design System(setup.sh:138-407,setup.ps1:133-356, as of 2026-07-11). - If you added a prompt, add its
CCF_*variable to BOTH non-interactive resolvers:setup.sh~lines 59-136 (${CCF_X:-default}plus a validationcase) andsetup.ps1~lines 51-131 (if ($env:CCF_X) {...} else {default}plus validation). CLAUDE.md ("Non-Interactive Setup") makes this mandatory. Also register the placeholder inconfig/placeholders.jsonif templates consume it. - Run the gates:
bash tests/check-placeholders.sh, thenbash tests/check-setup-smoke.sh, then fullbash tests/run-all.sh. - Exercise
setup.ps1yourself —pwsh -NoProfile -File tests/check-setup-smoke.ps1if you have pwsh, otherwise a manual-DryRunrun. Do not rely on run-all or CI here (see "How to verify parity" for why). - If your change alters install output or counts, hand off to ccf-doc-sync-campaign before calling it done.
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 · 123 lines · 117 tokens per session scan B 123228125d97
ccf-parity-playbook is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 117 tokens to every session and 3,501 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…