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/lttr/claude-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/lttr/claude-marketplace/cc)<a href="https://agentmods.dev/plugins/lttr/claude-marketplace/cc"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/cc/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/lttr/claude-marketplace/cc"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/cc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cc 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 13d 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",
"version": "2.15.1",
"description": "Claude Code authoring tools: create plugins, skills, commands, and introspect Claude Code internals",
"author": {
"name": "Lukas Trumm"
},
"keywords": [
"claude-code",
"plugin",
"skill",
"authoring",
"introspection",
"handoff",
"memory"
]
}
What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 358 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.
- 13d ago Changed e0fdc42983fe
- 27d ago Changed a778aea03094
- 1mo ago First seen · 18 lines scan A 6ab9c89165b6
cc is a plugin published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 14d 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
section-508
Expert Section 508 compliance advisor for US federal ICT accessibility — VPAT/ACR completion, WCAG 2.0 AA audits, remediation planning, PDF accessibility, procurement language, keyboard and screen reader testing, undue burden assessments, and agency compliance workflows.
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
understanding
Understand a topic, a bug, or a Claude Code workflow: minimal explanations, root-cause diagnosis, execution traces.
misticos
Standing rules and drift reminders.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.