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/bootstrapgit 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/bootstrap)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/bootstrap"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/bootstrap.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.00021 | $0.01158 |
| Opus 5 | $0.00010 | $0.00579 |
| Sonnet 5 | $0.00004 | $0.00232 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
bootstrap 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kaddo bootstrap
kaddo bootstrap creates the structural knowledge baseline Kaddo expects. It is not
"new-project bootstrap" — it is knowledge-baseline bootstrap and applies to every project type.
What changes by project.state is the template content and orientation, not whether bootstrap
applies:
| State | Orientation |
|---|---|
new |
intent — product vision, planned capabilities, initial technical direction |
pre-ai |
discovery — current state, observed capabilities, assumptions, open questions |
legacy |
risk — constraints, criticality, dependencies, technical debt, modernization |
bootstrap is deterministic: it never calls an LLM, never generates source code, never decides the
architecture, never installs agents/skills, and never runs scan/context/git. It writes starter
templates (with placeholders, assumptions and [open] questions) that you then refine with agents.
What it creates
The common baseline (files + directories), with state-aware content:
knowledge/business/business.md
knowledge/product/product.md
knowledge/product/capabilities.md
knowledge/tech/codebase.md
knowledge/tech/current-state.md
knowledge/tech/decisions/
knowledge/delivery/roadmap.md
knowledge/delivery/work-items/
Every generated file carries project_state: in its front matter. pre-ai and legacy templates
add discovery/risk sections (e.g. Observed technical signals, Risks of interpretation,
Critical dependencies, Modernization notes).
Existing capability discovery (pre-ai / legacy)
For existing projects, knowledge/product/capabilities.md is scaffolded as an evidence-backed
capability inventory, not a wishlist. The capability-agent fills it in a state-aware way:
- new → Planned Capability Definition (
[planned]capabilities). - pre-ai → Existing Capability Discovery — a
## Capability Domainsmap where capabilities are grouped by functional domain (### Domain: <name>with a Purpose + Evidence summary), each#### Capability:carrying aStatus(implemented/partial/inferred/risky/deprecated/unknown) with evidence (paths, routes, tables, functions), plus## Capability Gapsand## Roadmap Candidate Signals(each naming itsDomain+Related capability). - legacy → Legacy Capability Discovery — the same domain map plus
Criticality,Change risk,Operational dependencyandModernization notesper domain/capability.
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 · 105 lines · 21 tokens per session scan A f27041c49352
bootstrap is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,158 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.