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/contextgit 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/context)<a href="https://agentmods.dev/commands/kaddo-kdd/kaddo/context"><img src="https://agentmods.dev/badge/commands/kaddo-kdd/kaddo/context.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.00011 | $0.01465 |
| Opus 5 | $0.00005 | $0.00732 |
| Sonnet 5 | $0.00002 | $0.00293 |
| Haiku 4.5 | $0.00001 | $0.00146 |
Grade A, and why
context 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kaddo context
Assembles a context pack you can hand off to an LLM chat agent (Claude, ChatGPT, Cursor, Copilot, Windsurf…). It reads existing Kaddo artifacts and writes two files:
.kaddo/context-pack.md— compact, LLM-friendly markdown to paste into a chat..kaddo/context-pack.json— structured data for future tooling and automations.
Inputs
The command reads (each is optional except config):
.kaddo/config.yml # required — run `kaddo init` first
.kaddo/scan.json # scan baseline
.kaddo/modules.yml # mapped multirepo modules (if any)
knowledge/inventory.md # technical inventory
knowledge/knowledge.md # current knowledge
knowledge/delivery/roadmap.md # roadmap
knowledge/delivery/work-items/ # work item metadata (front matter only)
Missing files do not stop the command — their sections are marked under Missing Context so the LLM knows what is not yet available.
By default, the context pack includes only active Work Items: draft, ready,
in-progress and blocked. completed and archived are historical knowledge and are
excluded so old work does not dominate the LLM handoff.
External Knowledge
If you imported Knowledge Capsules (kaddo capsule add), the pack adds an
## External Knowledge section summarizing each external system (purpose · capabilities ·
contracts · owner · risks) — minimal context about systems you don't map as multirepo.
Roadmap candidates vs materialized
When knowledge/delivery/roadmap.md is present, the ## Roadmap section reports
candidates (parsed from any supported roadmap format),
materialized work items, and remaining candidates. The JSON exposes a roadmap object
(present, candidates, materialized, remaining) so the agent knows which candidates are
still waiting to become Work Items.
Mapped modules (multirepo)
If the project has modules registered with kaddo modules map, the pack adds a
## Mapped Modules section (and a mappedModules array in the JSON) listing each
module's type, repo path, owner, capabilities and which knowledge/tech/modules/<id>/
artifacts exist. Kaddo reads .kaddo/modules.yml and the module artifacts only — it
never scans the secondary repositories.
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 · 161 lines · 11 tokens per session scan A 8497c65e4d42
context is a command published in the GitHub repository Kaddo-kdd/kaddo (47 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,465 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.