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/overviewgit 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/overview)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/overview"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/overview.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.00007 | $0.01626 |
| Opus 5 | $0.00003 | $0.00813 |
| Sonnet 5 | $0.00001 | $0.00325 |
| Haiku 4.5 | $0.00001 | $0.00163 |
Grade A, and why
overview 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
These commands group into Kaddo's four operating moments — Base → Definition → Projection → Execution — which explain when each one is used.
Command responsibility matrix
Each command answers one question and has a clear next step:
| Command | Question answered | Suggested next |
|---|---|---|
kaddo init |
How do I start a Kaddo project? | kaddo bootstrap |
kaddo bootstrap |
What minimum knowledge should exist? | kaddo add agents, then kaddo context |
kaddo scan |
What technical signals exist in the repository? | kaddo explain or kaddo context |
kaddo context |
What should I give to an LLM? | Use the recommended agent (kaddo understand) |
kaddo understand |
What should I do now? | Execute the recommended action |
kaddo explain |
What does Kaddo know? | kaddo understand |
kaddo create --from roadmap |
How do roadmap candidates become Work Items? | Refine with the work-item-agent |
kaddo owners suggest |
Who owns this code? | kaddo guard |
kaddo guard |
Is knowledge drifting from code? | Update the affected knowledge |
kaddo add agents |
Which agents are available? | kaddo understand |
kaddo capsule export |
How do I share this project as external context? | refine with the capsule-agent, then share |
kaddo capsule add <path> |
How do I consume another system as external context? | kaddo context (External Knowledge) |
kaddo graph export |
How is my project knowledge connected? | open .kaddo/graph.mmd or run kaddo explain |
scan,context,explainandunderstandalso print this — a Question answered / Suggested next footer — at the end of their output, so the next step is always one glance away.
Recommended workflows
New project
init → bootstrap → add agents → context → business-agent → product-agent →
codebase-agent → roadmap-agent → create --from roadmap → work-item-agent →
implementation-agent
Active development
implementation-agent → scan → owners suggest → guard → explain
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 · 113 lines · 7 tokens per session scan A dbf194cd0535
overview is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 1,626 once invoked, about $0.0000 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.