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.
npx agentmods add commands/drabaioli/cdd/cdd-bootstrapgit clone --depth 1 https://github.com/drabaioli/cddWhat 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 | $0.00000 | $0.02320 |
| Opus 5 | $0.00000 | $0.01160 |
| Sonnet 5 | $0.00000 | $0.00464 |
| Haiku 4.5 | $0.00000 | $0.00232 |
Grade C, and why
cdd-bootstrap scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Then remove the overlay: `rm -rf "$OVERLAY"`. How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold a new greenfield project on the CDD workflow: /cdd-bootstrap (takes no argument).
Run this command from a CDD-repo session (it needs the CDD repo's template/ and bootstrap-cdd-project.sh). This command exists only in the CDD repo; it deliberately has no counterpart in template/.claude/commands/ (it operates on a new target project, so downstream projects have no use for it — see the process doc, Section 2.7). It is the greenfield sibling of /cdd-retrofit: /cdd-retrofit adapts an existing project, /cdd-bootstrap creates a new one.
This is a guided command, not a brief-to-files converter. The discovery conversation is part of the job: you walk the user through defining the project, then encode the result into the initial docs and roadmap, then scaffold the project in a single bootstrap invocation. The generated project starts with a real, filled-in overview, CLAUDE.md, and roadmap — not the template's pre-filled "survey the codebase" bootstrap phase, which is for files-only installs.
The command takes no argument: the project's name, directory, and location all emerge from the discovery conversation, so there is nothing meaningful to pass up front. The target path is proposed and confirmed in step 4, once the identifiers are settled.
Checkpoint discipline: confirm the project definition (step 1), then the draft roadmap (step 2), then the two identifiers and the target location (steps 3–4) — each before moving on. Nothing is rendered until all are approved. The scaffold commit is created only after the roadmap is approved. Outward-facing actions (creating a GitHub repo, editing ~/.bashrc) are confirmed separately and never done silently.
1. Guided discovery
Have a conversation to define the project. Do not dump a rigid questionnaire; ask in natural batches, probe vague or one-word answers, and reflect back what you heard. Cover, at minimum:
- What it is — one paragraph, plain terms.
- Goals — why it exists; the problem it solves or outcome it produces; what success looks like.
- What it does — the high-level capabilities, coarse-grained.
- What it explicitly does not do — the non-goals. Push for these; they are load-bearing and easy to skip.
- Constraints — language/platform, hard technical limits, regulatory/business constraints, compatibility, deadlines.
- Architecture intentions — intended high-level shape: major components, how they relate, external boundaries, structural principles the project commits to.
- Audience — who consumes it (end users, other services, a team, future-you).
- Engineering floor — what the project commits to for tested behaviour, continuous integration, lint & format, and dependency & toolchain hygiene (the negotiable rows of the template contract). Ask this as one batch: nothing exists yet to detect, so the answers are commitments, and most of them will honestly be expected.
The user may not have firm answers for everything; capture intent and mark genuinely open areas rather than inventing detail. This material becomes the project overview (doc/knowledge_base/project-overview.md) and seeds CLAUDE.md.
Off-ramp: if discovery reveals this isn't really a project — a single self-contained artifact, finished in essentially one sitting, used as-is by future-you — apply the shared scope-triage heuristic (doc/features/template.md, "Deliverable or project?") and offer to drop to /cdd-quick-create instead of scaffolding the full substrate. Surface the signals; the human decides.
Checkpoint: present a structured summary of the captured definition (the headings above). Get explicit confirmation or corrections before writing anything.
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.
- 2d ago First seen · 125 lines · 0 tokens per session scan C 72bfa4f1d24b
cdd-bootstrap is a command published in the GitHub repository drabaioli/cdd (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,320 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
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.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
docs-review
Phase 4 of documenting-projects: Quality gate with 8 measurable criteria and iteration. Triggers: '/docs-review', invoked by documenting-projects orchestrator.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.