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/initgit 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/init)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/init"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/init.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.00009 | $0.00473 |
| Opus 5 | $0.00005 | $0.00236 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
init 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 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.
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.
What it actually says
kaddo init
Creates the knowledge/ knowledge tree and .kaddo/config.yml.
knowledge/
knowledge.md ← current state of the product
roadmap.md ← intentions and priorities
work-items/ ← one file per work item
.kaddo/
config.yml ← project config
Project context
kaddo init asks three questions and records the answers in .kaddo/config.yml.
Other commands read this file to adapt their guidance — Kaddo becomes state-aware.
version: 1
project:
name: "my-app"
state: pre-ai # new | pre-ai | legacy
structure: monorepo # monorepo | multirepo
language: en # en | es — language of the project KNOWLEDGE
domains: []
team:
size: indie # indie | small | medium | enterprise
Project state — drives next-step guidance in scan and create:
| State | Meaning |
|---|---|
new |
Greenfield project; start defining knowledge from scratch. |
pre-ai |
Existing system without an AI/knowledge baseline yet. |
legacy |
Older system where risks and unknowns matter most. |
Team size — indie, small, medium, enterprise.
Repository structure — monorepo or multirepo.
Project language — en or es. This is the language of the project knowledge (templates,
agent outputs, context pack, roadmap, Work Items, ADRs, capabilities…), not the CLI. The CLI —
its commands, flags, prompts and messages — is always English. See
Project knowledge language.
Old config files keep working: missing fields fall back to safe defaults
(state: pre-ai, structure: monorepo, team.size: indie, language: en). Invalid enum values
produce a clear validation error listing the valid options.
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 · 58 lines · 9 tokens per session scan A 38e6b780fad2
init is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 473 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
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.