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/understandgit 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/understand)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/understand"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/understand.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.1 | $0.00015 | $0.02452 |
| Opus 5 | $0.00008 | $0.01226 |
| Sonnet 5 | $0.00003 | $0.00490 |
| Haiku 4.5 | $0.00002 | $0.00245 |
Grade A, and why
understand 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 6d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kaddo understand
Guides the handoff from the CLI (deterministic context) to your LLM (interpretation). It refreshes the context pack, recommends which agents to use — in what order — based on your project state, and writes a reusable guide you can re-open any time.
It writes / refreshes:
.kaddo/context-pack.mdand.kaddo/context-pack.json— the input for agents..kaddo/understand.md— the state-aware handoff guide with the current phase, recommended agent/skill, delivery state, primary and secondary recommendations, active Work Items, concrete agent/skill paths, and copy/paste instructions. The markdown matches the console output (VS-079.1).
What it does
- Requires an initialized project (
kaddo init). - Checks for a scan baseline (
.kaddo/scan.json) — warns but continues if missing. - Generates / refreshes the context pack (reuses
kaddo context). - Builds a state-aware agent plan and flags any agents not yet installed
(
kaddo add agents). - Prints a concise terminal summary and writes
.kaddo/understand.md.
Deterministic, no LLM
kaddo understand does not call an LLM, execute agents, or auto-generate architecture
artifacts. It prepares context and tells you exactly which agent to run next. You stay in
control of the interpretation.
State-aware agent flow
State-aware recommendations
understand recommends the next step from the real knowledge state — layers, roadmap, Work
Items and ownership — not only the project.state recorded by kaddo init. It reports the current
phase, the reason, the recommended agent(s) and a concrete next step:
Current phase: Active Delivery
Reason:
- Roadmap available
- 1 materialized work item(s)
- ready: 1
- Ownership coverage 100%
Recommended: implementation-agent
Next step: Start WI-014 — Create task (ready → in-progress)
Phases are derived from what actually exists:
| Phase | When |
|---|---|
| Discovery | base layers missing (business / product / codebase) |
| Planning | base knowledge exists, no roadmap yet |
| Delivery Preparation | roadmap exists, no Work Items yet |
| Active Delivery | active Work Items exist (draft / ready / in-progress / blocked) |
| Maintenance | Work Items completed and the roadmap is mostly materialized |
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.
- 6d ago First seen · 246 lines · 15 tokens per session scan A ed9e5849b544
understand is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 2,452 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.