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-architecture-contract/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-architecture-contract)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-architecture-contract"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-architecture-contract/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-architecture-contract"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-architecture-contract.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.00142 | $0.03497 |
| Opus 5.5 | $0.00057 | $0.01399 |
| Sonnet 5.5 | $0.00028 | $0.00699 |
| Haiku 4.5 | $0.00014 | $0.00350 |
Grade A, and why
ccf-architecture-contract 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.
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 Architecture Contract
The load-bearing design decisions of claude-code-framework, the invariants every change must preserve, and the currently open weak points. This is the "why" layer; sibling playbooks own the "how".
Usage
Load this skill when:
- Deciding where a new file belongs (distributable payload vs dogfooded config vs account-level skill).
- About to change setup.sh/setup.ps1 structure, config/*.json shape, or any documented count.
- A
tests/check-*.shfailure makes no sense until you know what invariant it protects. - Asked "is this a known issue?" — check the weak-points list below first.
Do NOT use this skill for: term definitions or the config/*.json field catalog (→ ccf-domain-reference); which count lives in which doc, or fixing drift (→ ccf-doc-sync-campaign); bash↔PowerShell mirroring mechanics (→ ccf-parity-playbook); drift-allowlist editing procedure (→ ccf-dogfood-and-drift).
The three-tier content model
This repo is the framework, not a target project — never run setup.sh here (see CLAUDE.md). Every file lives in exactly one tier:
| Tier | Paths | Installed by | Reaches target repos? |
|---|---|---|---|
| Distributable payload | templates/, skills/, workflows/, memory/ |
setup.sh / setup.ps1 copy into the target's .claude/ etc. |
Yes |
| Dogfood config | .claude/ |
Hand-curated; lives only here | No |
| Account-level skills | global-skills/ |
install-global-skill.sh / .ps1 → ~/.claude/skills/ |
No (installed per user account, not per repo) |
Why three tiers: the repo needs Claude Code tooling to work on itself, but running the installer here would overwrite the curated .claude/ with generic rendered output. So .claude/ is a deliberately reduced, hand-maintained subset, and every difference between it and templates/+skills/ must be listed in config/dogfood-drift-allowlist.txt or tests/check-dogfood-drift.sh fails (mechanics → ccf-dogfood-and-drift). global-skills/ exists because /install-framework must be available before any repo has the framework — it bootstraps installation, so it cannot itself be a per-repo template (see CLAUDE.md "Global Skills").
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 · 142 tokens per session scan A 5f652cab2267
ccf-architecture-contract is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 142 tokens to every session and 3,497 once invoked, about $0.0006 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
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…