Borrowing it
Nothing to install: this file belongs to drabaioli/cdd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/drabaioli/cdd/main/.claude/commands/cdd-quick-create.mdgit clone --depth 1 https://github.com/drabaioli/cddWrote 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-quick-create)<a href="https://agentmods.dev/commands/drabaioli/cdd/cdd-quick-create"><img src="https://agentmods.dev/badge/commands/drabaioli/cdd/cdd-quick-create/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/commands/drabaioli/cdd/cdd-quick-create"><img src="https://agentmods.dev/badge/commands/drabaioli/cdd/cdd-quick-create.svg" alt="Reviewed on agentmods" width="80" 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.01637 |
| Opus 5.5 | $0.00000 | $0.00655 |
| Sonnet 5.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 2mo 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.
- 2mo 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 yesterday), 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
pdca-plan
Run only the PLAN phase of the PDCA framework (1a analysis, then 1b detailed plan).
pdca-act
Run only the ACT phase of the PDCA framework (retrospective and continuous improvement).
pdca-check
Run only the CHECK phase of the PDCA framework (completeness validation).
pdca-do
Run only the DO phase of the PDCA framework (TDD implementation with active oversight).
pdca
Run the full PDCA framework cycle (Plan, Do, Check, Act) — alias for the pdca-framework skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.