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-debugging-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-debugging-playbook)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-debugging-playbook"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-debugging-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-debugging-playbook"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-debugging-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.00153 | $0.03714 |
| Opus 5.5 | $0.00061 | $0.01486 |
| Sonnet 5.5 | $0.00031 | $0.00743 |
| Haiku 4.5 | $0.00015 | $0.00371 |
Grade B, and why
ccf-debugging-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.
grep -rn "{{[A-Z_]*}}" .claude/ CLAUDE.md How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCF Debugging Playbook
Symptom → root cause triage for this repo's real failure modes. Every command below was verified against the repo as of 2026-07-11. Line numbers drift — re-verify via Provenance before trusting them.
Usage
Load this when something is broken and you don't yet know why: a red test in tests/, CI/local disagreement, a broken install in a target project, or a misbehaving hook. Once diagnosed, switch to the sibling that owns the fix (named per row below). NOT for "am I done?" gating (ccf-testing-and-qa), doc-count repair (ccf-doc-sync-campaign), or setup-script feature work (ccf-parity-playbook).
Process
- Reproduce narrowly. Run the single failing check:
bash tests/check-<name>.sh. Every check prints per-item PASS/FAIL detail — read it. - Classify via the triage table. If two causes fit, run the discriminating experiment in the topic sections.
- Fix at the root, together. Never hand-edit a count, allowlist line, or doc entry in isolation — change it together with the files it describes.
- Rerun the full gate:
bash tests/run-all.sh(8 bash checks; the PowerShell smoke is NOT in it — see "Local green, CI red").
Triage Table
| Symptom | First check | Likely cause | Fix / owning skill |
|---|---|---|---|
check-dogfood-drift: "Unexpected .claude/template drift" |
Did you (or a parallel session) add/edit anything under .claude/agents, hooks, skills, settings.local.json, or statusline? |
Real drift with no line in config/dogfood-drift-allowlist.txt (format = the exact diff output line, e.g. Only in .claude/skills: <name>) |
Sync the file with templates//skills/, or add the exact printed line with justification — ccf-dogfood-and-drift |
check-dogfood-drift: "Stale allowlist entries" |
Was a .claude/ file removed or synced back to its template? |
Allowlist line describes drift that no longer exists | Delete the stale line — ccf-dogfood-and-drift |
check-consistency FAILED |
The FAIL line names actual vs documented count and file (setup.sh or README.md) |
Something was added/removed without updating the summary phrases (N workflow skills, N AI agents, …), or a count was hand-edited |
Update files + counts together across all surfaces — ccf-doc-sync-campaign |
check-consistency shows documented="?" |
Was a summary line reworded? | The check greps exact phrases; rewording breaks extraction even if the number is right | Restore the phrase or extend the grep in tests/check-consistency.sh |
check-agent-registry FAILED |
Which of its 3 sub-checks failed | config/agents.json out of lockstep with templates/agents/*.md frontmatter, or agent name absent from README.md / templates/CLAUDE.md.template / docs/teams.md / docs/agents-commands-rules.md |
Update registry + frontmatter + all four docs together — ccf-doc-sync-campaign |
check-placeholders FAILED |
The FAIL line says which script lacks the token | New {{TOKEN}} has no replacement in setup.sh, setup.ps1, or config/placeholders.json (JSON counts as present for both) |
Add to BOTH scripts or to placeholders.json — ccf-parity-playbook |
| Setup smoke FAILED | The captured tmp-dir output the test prints on failure | Real setup.sh regression OR a harness bug | Run setup manually in a throwaway dir (below) |
| Suite green locally, CI red (or vice versa) | command -v python3; git --version; git config --get commit.gpgsign |
python3 absence, git < 2.28, host signing config, or the ps1-only CI job | "Local green, CI red" below |
Leftover {{TOKEN}} in an installed project |
Which file family contains it | One of three replacement sites failed | "Tracing leftover placeholders" below |
| Hook misbehaving / never firing | Pipe JSON manually (below); check the event name in settings | Bad stdin parsing, missing jq/python3, or invalid event name | "Hook debugging" below |
| Setup "succeeded" but project half-configured | grep Traceback on captured setup output; validate config/*.json |
The eval "$(python3 …)" set -e blind spot |
"Silent half-configuration" below |
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 · 139 lines · 153 tokens per session scan B 40d051615be3
ccf-debugging-playbook is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 153 tokens to every session and 3,714 once invoked, about $0.0006 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.