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/kulmam92/cc-best-practices-marketplaceWrote 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/kulmam92/cc-best-practices-marketplace/cc-best-practices)<a href="https://agentmods.dev/plugins/kulmam92/cc-best-practices-marketplace/cc-best-practices"><img src="https://agentmods.dev/badge/plugins/kulmam92/cc-best-practices-marketplace/cc-best-practices/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/plugins/kulmam92/cc-best-practices-marketplace/cc-best-practices"><img src="https://agentmods.dev/badge/plugins/kulmam92/cc-best-practices-marketplace/cc-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cc-best-practices 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 10d 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": "cc-best-practices",
"version": "2.4.0",
"description": "Compound engineering: every session leaves your setup smarter. Verify, learn, audit, refactor -- with hooks, rules, and skills that prevent discipline decay.",
"author": {
"name": "kulmam92"
},
"repository": "https://github.com/kulmam92/cc-best-practices-marketplace",
"license": "MIT",
"keywords": [
"best-practices",
"workflow",
"boris-cherny",
"agentic-coding",
"verification",
"hooks",
"discipline"
]
}
What it installs
The manifest is a name and a version. 6 skills, 1 hook travel with it, and installing the plugin installs all of them — 316 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 10d ago First seen · 20 lines scan A 8ad4b88a3b98
cc-best-practices is a plugin published in the GitHub repository kulmam92/cc-best-practices-marketplace (2 stars, last pushed 5mo 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-08-31.
Other plugins, from other repositories
rust-dev
Rust development toolkit with best practices, code review, performance optimization, and async Rust patterns.
session-checkpoint
Session closer — saves context before compact. Handoff file, memory updates, lesson extraction, reflexion (what went wrong, what to improve).
electron-playwright-validator
Electron app UI automation and validation via Playwright CDP.
workflow
End-to-end issue workflows that orchestrate analysis, planning, implementation, verification, and shipping.
dev-workflow-bundle
Development workflow bundle (includes peer + extract-rules + dev-workflow + rules-review + tidy + prose-polish + mobpro + kabeuchi + artifactor).
linear
Manage Linear issues through a secure JSON-first CLI without MCP.