Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add bo-cao/breaking-coding-chaos --skill bcc-throughlinegit clone --depth 1 https://github.com/bo-cao/breaking-coding-chaosWrote 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/bo-cao/breaking-coding-chaos/bcc-throughline)<a href="https://agentmods.dev/skills/bo-cao/breaking-coding-chaos/bcc-throughline"><img src="https://agentmods.dev/badge/skills/bo-cao/breaking-coding-chaos/bcc-throughline.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.02539 |
| Opus 5 | $0.00028 | $0.01269 |
| Sonnet 5 | $0.00011 | $0.00508 |
| Haiku 4.5 | $0.00006 | $0.00254 |
Grade A, and why
bcc-throughline 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 8d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bcc-throughline
Job: keep a durable endeavor map so the human can see progress and re-order work — goal, phases, hardpoints, what changed.
Files (project root only): plans.md · progress.md · findings.md
Templates: templates/. Coding checklists live in root PLAN.md (other skills) — not here.
Internal only: disk = durable context; chat = RAM. Session file: SESSION.md. Writeback rules: WRITEBACK.md.
Do not narrate these metaphors or protocol names to the user unless they ask how BCC works.
User voice (required — comfort first)
Talk like a sharp collaborator mapping the project — not like a workflow product or a gatekeeper.
| Do | Don't |
|---|---|
| Lead with their goal / map / options | Lead with “先恢复上下文 / 对齐账本 / BCC 流程” |
| Short: goal → map (or delta) → 1–2 next choices | Dump file-role tables, 5-question grids, skill lecture |
| Suggest only map-level things (order, balance, drop/merge hardpoints) | Remind “还没写代码 / Throughline 不写产品代码 / 不进 plan-spar” unprompted |
| On cold start: act like starting | Act like resuming an empty project |
| Offer: “要继续 refining 主线的话可以说…” | Push the next BCC skill by default |
Length: prefer ≤ ~15 short lines of chat after tools (or one tight table of hardpoints). Longer only if the map itself is long.
Meta talk: role boundaries and “no product code” are agent constraints — enforce silently. Explain only if the user asks to code here, or asks what throughline is.
Branch: cold start vs resume
Before tools, classify silently:
| State | Signs | Do |
|---|---|---|
| Cold start | No trio, or empty workspace + user brings a new idea | Bootstrap map from their idea. Do not say restore/align context. |
| Resume / adjust | Trio exists; status, rebalance, reprioritize, after /clear |
Read trio (and session if present); update; answer briefly. |
| Lagging ledger | Code/git moved but files stale | Quietly reconcile files, then answer from the map. |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 215 lines · 56 tokens per session scan A e92a0f40b3e6
bcc-throughline is a skill published in the GitHub repository bo-cao/breaking-coding-chaos (22 stars, last pushed 5d ago), licensed MIT. It adds 56 tokens to every session and 2,539 once invoked, about $0.0003 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-30.
Other skills, from other repositories
handoff
Guides the Claude Code agent through completing a task, selecting a handoff tier, building a valid completion-card, and performing a clean task handoff.
generate-stories
Translate a single Epic into clear, actionable User Stories with explicit acceptance criteria. Activate when an Epic is defined and work needs to be prepared for Delivery execution.
review-input
Adversarial review of any input (human idea, agent analysis, research report, feedback, observation) BEFORE it mutates persistent project state. Universal interceptor with domain auto-detection, 2-phase classification + evaluation, and triple-verdict output (veracity / fit / actionability). Anti-girouette guardrail…
validate-artefacts
Validate that all Discovery artefacts (Epics, Stories) are clear, governed, complete, and safe to pass into Delivery. Activate after generating Epics or Stories and before any Delivery planning. This is the mandatory Discovery → Delivery gate.
coordinate-handoffs
Validate sub-agent handoff artefacts, sequence phase transitions, and manage retry and escalation logic. Activate after each sub-agent terminates to determine next action.
review-story-alignment
Adversarial review of generated stories against the Discovery Session Brief, referenced DECs, and Epic DoR. Detects contradictions, omissions, and intent drift BEFORE stories reach Delivery. Produces a structured verdict (PASS/FAIL) with specific findings per story. Triggers after generate-stories, before backlog…