Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/commands/drabaioli/cdd/cdd-retrofit)<a href="https://agentmods.dev/commands/drabaioli/cdd/cdd-retrofit"><img src="https://agentmods.dev/badge/commands/drabaioli/cdd/cdd-retrofit.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.04094 |
| Opus 5 | $0.00000 | $0.02047 |
| Sonnet 5 | $0.00000 | $0.00819 |
| Haiku 4.5 | $0.00000 | $0.00409 |
Grade A, and why
cdd-retrofit 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 6d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install CDD into an existing project, or upgrade a project already running CDD, at the path given as argument: /cdd-retrofit <target-path>.
Run this command from a CDD-repo session (it needs the CDD repo's template/, bootstrap-cdd-project.sh, and git history). The mode — install or upgrade — is auto-detected from the target. This command exists only in the CDD repo; it deliberately has no counterpart in template/.claude/commands/ (it operates on target projects, so downstream projects have no use for it — see the process doc, Section 2.7).
Checkpoint discipline: every write that touches a pre-existing file in the target is approved per file by the user. Never overwrite a project file silently. Identifier choices (name/slug/dir) are confirmed before anything is rendered.
Target path: $ARGUMENTS
1. Resolve and validate the target
Resolve the argument to an absolute path. It must exist and be a directory; otherwise stop and report.
Check the target's git state:
git -C <target> rev-parse --is-inside-work-tree 2>/dev/null
git -C <target> status --porcelain 2>/dev/null
- If the target is not a git repo, warn the user (retrofit changes won't be revertable via git, and the isolated-worktree step in section 2.5 won't run) and ask whether to proceed.
- A dirty working tree no longer blocks the retrofit: section 2.5 writes into a fresh worktree branched from HEAD, so the target's current checkout is untouched. Do not hard-stop on a dirty tree. There is one nuance to warn about: because the worktree is taken from HEAD, any uncommitted local edits to CDD-managed files (the set listed in section 4.4) are invisible to the upgrade comparison. If
git status --porcelainshows uncommitted changes to those files, tell the user to commit them first or they won't be considered, then let them decide whether to proceed.
Also note <target>/.gitignore: if any path the retrofit will write (.claude/, doc/, tools/) is gitignored, warn that those writes will not show in git status (and won't be staged by the retrofit commit in sections 3.4 / 4.6), and include this in the final summary.
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.
- 6d ago First seen · 209 lines · 0 tokens per session scan A f2cfd72edf37
cdd-retrofit is a command published in the GitHub repository drabaioli/cdd (2 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,094 tokens. 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
catchup
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/catchup/SKILL.md.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
cost-tracker
Track session costs, understand token spend, and get optimization tips.