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.
git 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/plugins/bo-cao/breaking-coding-chaos/bcc)<a href="https://agentmods.dev/plugins/bo-cao/breaking-coding-chaos/bcc"><img src="https://agentmods.dev/badge/plugins/bo-cao/breaking-coding-chaos/bcc.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bcc 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 4d 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.
What it actually says
{
"name": "bcc",
"source": "./",
"description": "Breaking Coding Chaos: four dual-loop skills (main + throughline + plan-spar + clean-cut)",
"version": "1.0.0",
"strict": false,
"author": {
"name": "bo-cao"
},
"homepage": "https://github.com/bo-cao/breaking-coding-chaos",
"repository": "https://github.com/bo-cao/breaking-coding-chaos",
"license": "MIT",
"keywords": [
"skills",
"planning",
"hitl",
"dual-loop"
],
"category": "productivity",
"skills": [
"./skills/bcc-breaking-coding-chaos",
"./skills/bcc-throughline",
"./skills/bcc-plan-spar",
"./skills/bcc-clean-cut"
]
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 303 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#bcc 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.
- 4d ago First seen · 26 lines scan A 75407ca954b4
bcc is a plugin published in the GitHub repository bo-cao/breaking-coding-chaos (22 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
concord-relay
Delivers Concord inter-agent messages into a running Claude Code session, whether it is mid-task or idle at the prompt.
supericons
Search, preview, recommend, and retrieve SVG icons by meaning through Supericons MCP.
krimto
Open-source memory for AI coding agents you own in git — governed by a real user→team→org hierarchy, not a vendor database. Solo to team. Apache-2.0.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.