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/rube-de/cc-skillsWrote 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/rube-de/cc-skills/cdt)<a href="https://agentmods.dev/plugins/rube-de/cc-skills/cdt"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/cdt/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/rube-de/cc-skills/cdt"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/cdt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cdt 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 5d 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": "cdt",
"description": "Multi-agent development workflow with five modes: plan, dev, full, auto, and bugfix. Uses Agent Teams for collaborative roles (Architect, PM, Developer, Tester, Reviewer) and a Researcher subagent for documentation lookups via Context7.",
"version": "2.20.1",
"source": "./plugins/cdt",
"category": "development",
"author": {
"name": "rube-de",
"url": "https://github.com/rube-de"
},
"keywords": [
"agent-teams",
"multi-agent",
"planning",
"development",
"code-review",
"testing"
]
}What it installs
The manifest is a name and a version. 1 skill, 5 commands, 1 agent, 4 hooks travel with it, and installing the plugin installs all of them — 469 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill cdt A 115 tokens
- Command bugfix A 60 tokens
- Command dev-task A 43 tokens
- Command plan-task A 31 tokens
- Command auto-task C 42 tokens
- Command full-task C 39 tokens
- Agent researcher A 139 tokens
- Hook UserPromptSubmit A not measured
- Hook PreToolUse A not measured
- Hook Stop A not measured
- Hook SessionStart A not measured
What ships with it
1 file beside marketplace.json#cdt 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.
- 5d ago Changed def737801155
- 9d ago Changed 409ad142d332
- 10d ago Changed f05b652064b2
- 10d ago Changed dc596decc1a7
- 13d ago Changed 0e13a1312c7b
- 23d ago Changed 70952b4cbc7c
- 1mo ago Changed 16df96f2ebbd
- 1mo ago First seen · 19 lines scan A f1a2f9b5f08d
cdt is a plugin published in the GitHub repository rube-de/cc-skills (10 stars, last pushed yesterday), 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
review-all
Comprehensive, project-agnostic, multi-agent code review for Claude Code with verification to eliminate false positives.
great-cto
You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 72 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.
cursor
Local Cursor Agent CLI delegation: multi family consults, Composer implementation in owned worktrees, review, resumable history, background jobs, and setup health checks.
asdlc
PRD Implementor, PR Review, PDQC, Jira leg — commands and subagents.
agent-harness
Multi-agent harness for Claude Code: Planner→Generator→Evaluator sprints executed as background dynamic workflows (Agent-tool fallback), fable/opus/sonnet/haiku model routing with per-role reasoning effort, harness-engineering framework for design/diagnosis, and Anthropic 2026-04-04 P-G-E pattern.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.