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-next-stepgit 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-next-step)<a href="https://agentmods.dev/commands/drabaioli/cdd/cdd-next-step"><img src="https://agentmods.dev/badge/commands/drabaioli/cdd/cdd-next-step.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 | $0.00000 | $0.03085 |
| Opus 5 | $0.00000 | $0.01543 |
| Sonnet 5 | $0.00000 | $0.00617 |
| Haiku 4.5 | $0.00000 | $0.00309 |
Grade C, and why
cdd-next-step scanned grade C with 2 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/drabaioli/cdd/main/tools/cdd-worktree.sh --create-dirs -o ~/.cdd/tools/cdd-worktree.sh && bash ~/.cdd/tools/cdd-worktree.sh install Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/drabaioli/cdd/main/tools/cdd-worktree.sh --create-dirs -o ~/.cdd/tools/cdd-worktree.sh && bash ~/.cdd/tools/cdd-worktree.sh install How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope the next roadmap task and produce a handoff file for a fresh implementation session.
This is the exploratory-session command. Run on the main worktree. Output is a handoff file that a later, isolated implementation session will consume. This session does not modify any file in the repo; the only artifact it produces is the handoff file under ~/.cdd/handoffs/cdd/.
0. Mode: roadmap-driven, intent-driven, or issue-driven
This command has one optional argument. Dispatch on its shape:
$ARGUMENTS |
Mode | Branches at |
|---|---|---|
| empty | roadmap-driven | §3 |
#123 or a bare integer 123 |
issue-driven, direct | §0b |
issue or issues |
issue-driven, browse | §0b |
| anything else | intent-driven | §3-intent |
Every mode first runs §0a (checkout freshness), §1 (read context) and §2 (stale-handoff sweep); the "Branches at" column is only where the mode-specific path begins after that.
- Roadmap-driven: pick the next item off the roadmap. Run §1–§8 as written.
- Intent-driven: the task is already chosen by the user, so skip candidate proposal (§3 is replaced by §3-intent below). Use this when the user wants to start something off-roadmap rather than picking the next checkbox.
- Issue-driven: a thin front-end onto intent-driven mode — the intent text comes from a GitHub issue instead of being typed. §0b resolves the issue, then the flow is exactly intent-driven (§1 adaptive load, §3-intent, §4 onward).
All modes converge on the same machinery from §4 onward (stale-handoff sweep in §2 runs in all of them). Do not fork the flow beyond what §0b, §1, and §3 describe.
0a. Verify the checkout is current
Scoping work from a stale checkout can hand off a task that is already merged, so before reading any context, confirm this checkout is not behind its upstream. Compare the checked-out branch — the branch a task cut here would be based on (§4) — against its upstream, not the platform default branch:
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.
- 3d ago First seen · 208 lines · 0 tokens per session scan C 24ba2d8549e5
cdd-next-step is a command published in the GitHub repository drabaioli/cdd (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,085 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
set-tracker
Set the issue tracker for the current project.
maggy-init
Interactive wizard that configures Maggy for the user's org, issue tracker, and codebases. Writes /.maggy/config.yaml and ensures deps are installed.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
_docs_vivas
Protocolo interno de documentación viva: qué fichero se actualiza en cada gate.
progress
Resumen operativo del proyecto: progreso, kanban, bloqueos y trazabilidad.