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/explaingit 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/explain)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/explain"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/explain.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.00020 | $0.02226 |
| Opus 5 | $0.00010 | $0.01113 |
| Sonnet 5 | $0.00004 | $0.00445 |
| Haiku 4.5 | $0.00002 | $0.00223 |
Grade A, and why
explain 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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kaddo explain # project explanation (human-readable)
kaddo explain --for human # same, explicit
kaddo explain --for agent # compact structured JSON
kaddo explain --scope payments # focused: limit to a domain or keyword
kaddo explain --type adr # focused: limit to one artifact type
kaddo explain --since 2026-01-01 # focused: limit by creation date
Project explanation (no filters)
Run without filters, kaddo explain summarizes the current state of the
project from existing Kaddo artifacts:
- Project metadata (name, state, team, structure)
- Detected stack (from
.kaddo/scan.json) - Knowledge status (inventory, context pack, capabilities, architecture baseline, roadmap, agents)
- Work Items counted by lifecycle state (
draft,ready,in-progress,blocked,completed,archived) - Ownership coverage (how many work items declare
code:globs) - Missing knowledge and suggested next steps
It also writes .kaddo/explain.md and .kaddo/explain.json so the explanation
can be reused for onboarding, handoff or by agents. No LLM is called — the
output is fully deterministic.
# Project Explanation
## Project
- Name: dotear-web
- State: pre-ai
- Team: indie
- Structure: monorepo
## Detected Stack
- Language: TypeScript
- Framework: Next.js
## Knowledge Status
- Capabilities: missing
- Roadmap: available
- Roadmap candidates: 21
- Materialized work items: 5
- Remaining candidates: 16
- Ownership coverage: 1/2 work items
## Suggested Next Steps
1. Use capability-agent to create knowledge/product/capabilities.md.
2. Materialize 16 roadmap candidate(s) with `kaddo create --from roadmap`.
3. Run `kaddo owners suggest` for Work Items without code ownership.
explain also reports the Work Items by Type distribution (Features / Bugfixes / Hotfixes /
Spikes / Chores), so technical and maintenance work (chore) stays visible and distinct from
delivered features:
## Work Items by Type
- Features: 12
- Chores: 4
- Spikes: 2
- Bugfixes: 1
explain also flags possible duplicate Work Items (non-blocking) — items sharing the same
roadmap source candidate or the same normalized title (which catches translated duplicates like
Initialize TypeScript CLI project / Inicializar proyecto TypeScript CLI). Review them before
continuing.
When a roadmap is present, explain distinguishes roadmap candidates (entries the
roadmap-agent proposed) from materialized Work Items (created under
knowledge/delivery/work-items/). The remaining candidates count is the gap between them, and
explain suggests materializing them with kaddo create --from roadmap. Candidates are read from
any supported roadmap format (table, bullet,
checklist, mixed initiatives, or the strict Kaddo Roadmap Agent format).
explain also groups Work Items virtually by initiative front matter. Phase and initiative
remain metadata for planning and functional traceability; folders represent lifecycle state only.
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.
- 4d ago First seen · 198 lines · 20 tokens per session scan A 324db06978c5
explain is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 2,226 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
git
Git operations with intelligent commit messages and workflow optimization.
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.