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-quick-creategit 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.01637 |
| Opus 5 | $0.00000 | $0.00818 |
| Sonnet 5 | $0.00000 | $0.00327 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
cdd-quick-create 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 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.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a small, self-contained deliverable — a script plus a README, not a full CDD project: /cdd-quick-create (takes an optional one-line description of what to build).
Run this command from a CDD-repo session. It is the third sibling of /cdd-bootstrap and /cdd-retrofit: /cdd-bootstrap creates a new CDD project, /cdd-retrofit adapts an existing one, and /cdd-quick-create creates a lightweight deliverable — a one-off artifact with none of the project substrate (no roadmap, no doc/ tree, no .claude/commands/, no worktree helper, no baseline marker, no /cdd-pre-pr lifecycle). Like its siblings it exists only in the CDD repo and has no counterpart in template/.claude/commands/; unlike them it needs neither template/ nor the bootstrap script, because a one-off has no template — it writes plain files directly (see doc/features/template.md).
This is a guided command, but deliberately lighter than /cdd-bootstrap: a few natural questions, not the seven discovery headings. What it keeps from CDD is the part that pays off even for a one-off — a little guided discovery, clean single-purpose code, and a README so future-you can use it. What it drops is everything a single artifact doesn't need.
Checkpoint discipline: confirm the scope (step 1), then the captured definition (step 2), then the name and target (step 3) — each before moving on. The deliverable is written files-first (step 4), before any version control. The two outward-facing actions — a local commit (step 6) and a GitHub repo (step 7) — are offered separately, confirmed individually, and never done silently or by default.
1. Scope check (the gate)
Before discovery, confirm this is actually a deliverable and not a project. Apply the shared scope-triage heuristic (doc/features/template.md, "Deliverable or project?"): a task is a project (→ /cdd-bootstrap) when any of these hold — it is expected to evolve across many sessions and needs a roadmap; it has more than one cooperating component or an architecture worth documenting; it involves multiple collaborators or handoffs; it is long-lived and will accrete features. It is a deliverable (→ /cdd-quick-create) when none hold: a single self-contained artifact, finished in essentially one sitting, used as-is by future-you.
If, from the description ($ARGUMENTS) or an opening exchange, project-signals trip, surface them and offer to switch to /cdd-bootstrap rather than proceeding. The human decides.
Checkpoint: if any project-signal is present, name it and get an explicit "stay lightweight" or "switch to /cdd-bootstrap" before continuing.
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 · 93 lines · 0 tokens per session scan A 3ef983936f12
cdd-quick-create 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 1,637 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
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.