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/kaddo-kdd/kaddo/readygit clone --depth 1 https://github.com/Kaddo-kdd/kaddoWrote 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/kaddo-kdd/kaddo/ready)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/ready"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/ready.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.00013 | $0.00633 |
| Opus 5 | $0.00006 | $0.00316 |
| Sonnet 5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
ready 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kaddo ready WI-001
Transitions a draft Work Item to ready after human review. This is the explicit approval
step between refinement (work-item-agent) and implementation (implementation-agent).
What it does
- Finds the Work Item by ID across all lifecycle folders.
- Shows a summary: type, knowledge level, domains, source, code ownership, acceptance criteria count, and any warnings.
- Asks for confirmation (unless
--yesis passed). - Updates
status: draft→status: readyin the frontmatter. - Adds a
ready_attimestamp. - Moves the file from
work-items/draft/towork-items/ready/.
Warnings
Before confirming, Kaddo checks for common issues:
- No acceptance criteria section found.
- No code ownership globs declared.
- No validation section found.
- Open questions still present (ignored if marked as "None", "Resolved", or "Deferred").
- No domains declared.
Warnings are advisory — the user can proceed anyway.
Options
| Flag | Description |
|---|---|
--yes |
Skip the confirmation prompt. |
After marking ready
Run kaddo context && kaddo understand to refresh the handoff. Kaddo will switch from
recommending work-item-agent to implementation-agent.
kaddo ready WI-001
kaddo context
kaddo understand
Design principles
- Human approval: agents refine, humans approve.
kaddo readyis the approval gate. - Ready ≠ implemented: marking ready means the scope is clear, not that code exists.
- No LLM, no git: the command is fully deterministic and never mutates version control.
- Metadata preserved: source, domains, code globs, generated_by, template_version, and the full markdown body are untouched.
Example
┌ kaddo ready WI-001
│
● Work Item found:
│ WI-001 — Listar últimas compras en reportes de métricas generales
│
● Status: draft → ready
● Type: bugfix
● Knowledge level: K2
● Domains: loyalty
● Source: manual
● Code ownership:
│ - src/hooks/useAdminMetrics.ts
│ - src/app/dashboard/page.tsx
│
◇ Mark this Work Item as ready for implementation?
│ Yes
│
◆ Updated status: ready
◆ Moved file:
│ knowledge/delivery/work-items/draft/WI-001-...md
│ → knowledge/delivery/work-items/ready/WI-001-...md
│
└ Work Item WI-001 is ready.
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.
- 5d ago First seen · 87 lines · 13 tokens per session scan A 6a9770d87dc0
ready is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 633 once invoked, about $0.0001 per session on Opus 5. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.