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-build-and-env/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-build-and-env)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-build-and-env"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-build-and-env/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-build-and-env"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-build-and-env.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.00144 | $0.03239 |
| Opus 5.5 | $0.00058 | $0.01296 |
| Sonnet 5.5 | $0.00029 | $0.00648 |
| Haiku 4.5 | $0.00014 | $0.00324 |
Grade B, and why
ccf-build-and-env scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -r "{{" .claude/ CLAUDE.md | grep -v ".git" # must print nothing Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| jq, sqlite3, curl (optional) | Only `templates/hooks/codebase-index.sh` at *target-project* runtime | `command -v jq sqlite3 curl` | Framework tests never invoke that hook; you only need these to exercise it manually ( How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCF Build & Environment
Usage
Load this skill when you need a working development environment for this repo (the framework itself): first clone, new machine, or proving your environment is healthy before/after changes. Also load it when a "works here, fails there" symptom smells environmental (missing python3, missing pwsh, macOS-vs-Linux tooling).
Do NOT use this skill for:
- What each test gates or how to extend the suite → ccf-testing-and-qa
- setup.sh/setup.ps1 flags, CCF_* variables, install/rollback into target projects → ccf-release-and-install
- Why
.claude/differs fromtemplates/and the drift allowlist → ccf-dogfood-and-drift - A failing check's design intent → ccf-architecture-contract
Process: clone to verified
There is no build step. "Environment works" means the test suite passes.
git clone https://github.com/BostonOrange/claude-code-framework.git
cd claude-code-framework
python3 --version # MUST print a version — see Trap 2 before trusting a green suite without it
bash tests/run-all.sh
Expected tail of step 4 on a clean clone (verified 2026-07-11):
RESULT: ALL TESTS PASSED (8 of 8)
Anything else: match the failing check name against ccf-testing-and-qa (what it gates) and ccf-debugging-playbook (triage). One known-benign case: check-dogfood-drift fails whenever you have untracked files under .claude/ (see Trap 3).
What this repo is
claude-code-framework is markdown + bash + PowerShell + JSON. There is nothing to compile, no npm install, no virtualenv, no lockfile to restore for framework work. The vendored app template templates/internal-nextjs-business-app/ contains a package-lock.json, but it is payload that setup.sh copies into target projects — you never install its dependencies to develop the framework (the only npm install string in setup.sh is documentation text it generates for target projects, line ~593). Full vocabulary/object model: ccf-domain-reference.
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 · 136 lines · 144 tokens per session scan B 53c7bdc92eb0
ccf-build-and-env is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 144 tokens to every session and 3,239 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). 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…