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-onboarding-tour/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-onboarding-tour)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-onboarding-tour"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-onboarding-tour.svg" alt="Measured on agentmods" 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.03383 |
| Opus 5 | $0.00057 | $0.01691 |
| Sonnet 5 | $0.00023 | $0.00677 |
| Haiku 4.5 | $0.00011 | $0.00338 |
Grade A, and why
ccf-onboarding-tour 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 7d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCF Onboarding Tour
A guided reading order for the claude-code-framework repo: ten stops, in sequence, each with what to NOTICE (~45 minutes for a human, one pass for a model session). Read-only orientation — it never tells you how to change anything; actions route to siblings via the table at the end.
Context in one sentence: this repo IS the framework (skills/agents/commands/rules/hooks as markdown + bash), installed into target projects by setup.sh / setup.ps1 with {{PLACEHOLDER}} substitution — it is never itself a target. The invariants behind each "notice" bullet are owned by ccf-architecture-contract; this tour only points at their footprints.
Usage
Load when: it is your first session in this repo; you were handed a task ("fix X", "add a skill") with no prior context; or someone asks "how does this all fit together?".
Do NOT load when: you already know the repo and need vocabulary or counts (→ ccf-domain-reference), you're mid-change and need gating rules (→ ccf-change-control), or a test just failed (→ ccf-testing-and-qa). This tour will not tell you how to do anything — it exists so the other skills make sense faster.
Process: the tour, in order
Read the stops in order — each builds on the previous. Commands are copy-pasteable from the repo root. Line counts and numbers are anchors (as of 2026-07-11); if they've drifted, trust the repo, not the tour.
Stop 1 — CLAUDE.md (repo root)
Notice:
- The first bold sentence: "This repo is the framework itself, NOT a target project. Do not run setup.sh here." Most confusion here traces back to forgetting this.
- The Agents Available table lists 39 template agents; the note beneath flags
framework-qaas in-repo-only. Counts like "27 workflow skills", "39 agents", "23 rules" recur across many files — doc/count drift is the maintainer's hardest live problem, and the discipline is: never hand-edit a count in isolation; counts change only together with the files they count, verified by tests (owned by ccf-doc-sync-campaign). - The Self-Improvement section: sessions that modify framework files end with
/improve+framework-qa, withtests/run-all.shas the deterministic hard gate (owned by ccf-change-control).
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.
- 7d ago First seen · 158 lines · 114 tokens per session scan A 42b14429e521
ccf-onboarding-tour is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 114 tokens to every session and 3,383 once invoked, about $0.0006 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…