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-failure-archaeology/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-failure-archaeology)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/ccf-failure-archaeology"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-failure-archaeology/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-failure-archaeology"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/ccf-failure-archaeology.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.00150 | $0.04086 |
| Opus 5.5 | $0.00060 | $0.01634 |
| Sonnet 5.5 | $0.00030 | $0.00817 |
| Haiku 4.5 | $0.00015 | $0.00409 |
Grade A, and why
ccf-failure-archaeology 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Failure Archaeology — the Chronicle of Settled Battles
The repo's incident history: significant investigations, dead ends, and re-fixes, written up so nobody rediscovers a root cause already in git log. Every hash was re-verified against this repo on 2026-07-11 with git show <hash> and git branch -a --contains <hash>.
Status vocabulary: fixed-on-main (merged, done), merged-2026-07-11 (was stranded on origin/claude/codebase-assessment-7p9rq7 from 2026-06-11 until that branch was merged on 2026-07-11), open (known, unfixed), settled-decision (deliberately rejected — do not reintroduce).
Usage
Load this when a symptom matches an entry (the Edge Cases table maps symptoms to entries), when about to propose something the repo already tried and removed (pre-commit git hooks, a broad refactor agent), or when asking what the assessment branch contained before it merged.
Do NOT load this for: the current doc-drift fix campaign (ccf-doc-sync-campaign), what each test gates today (ccf-testing-and-qa), bash/PowerShell mirroring procedure (ccf-parity-playbook), or merge gating (ccf-change-control). This skill is history and judgment; siblings own current state and procedure.
Entry 1 — The PowerShell smoke chain (flagship)
The single most instructive incident in this repo's history. Three commits, three layers of failure; the first fix landed immediately, the other two sat stranded on a side branch for a month before merging on 2026-07-11.
Chapter 1: 42e6a98 (2026-05-28, fixed-on-main).
- Symptom:
setup.ps1threw parser errors under Windows PowerShell 5.1 (nopwshinstalled). - Root cause: without a UTF-8 BOM, WPS 5.1 read the file as ANSI and mis-decoded an em-dash in the pre-commit sentinel string as a smart quote, closing the string early. Fix: add the BOM (a 1-line change to
setup.ps1). - Lesson:
setup.ps1must keep its UTF-8 BOM forever; the em-dash sentinel must byte-matchsetup.shand the installed hook.
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 · 134 lines · 150 tokens per session scan A 7ab7e799e1f6
ccf-failure-archaeology is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 150 tokens to every session and 4,086 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
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.