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.
git clone --depth 1 https://github.com/aahlijia/dekkoWrote 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/aahlijia/dekko/map)<a href="https://agentmods.dev/commands/aahlijia/dekko/map"><img src="https://agentmods.dev/badge/commands/aahlijia/dekko/map/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/aahlijia/dekko/map"><img src="https://agentmods.dev/badge/commands/aahlijia/dekko/map.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00450 |
| Opus 5.5 | $0.00008 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
map 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 26d 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
Code map results
The map has been (re)generated and a compact digest printed below.
!dekko map --if-stale . $ARGUMENTS
!dekko summary --budget 2000
Your task
The repository map was generated programmatically by the tool above — do NOT parse any source files yourself.
- If the output above shows an error, explain the problem to the user
and how to fix it. In particular, if the
dekkocommand was not found, tell them to install it withpip install dekko(oruv tool install dekko); for any other install/environment error, point them at/doctor. Otherwise: - Relay the digest to the user: the file/symbol/edge counts and language mix, the largest directories and what they do, the load-bearing and orchestrating symbols, and any parse errors.
- Tell the user the full map is at
.dekko/MAP.md(human-readable) and.dekko/map.json(machine-readable), and that they can query it without re-reading source viadekko search|query|context|affectedor the dekko MCP tools (search_code,query_symbol,get_context_pack,outline,workset,impacted_tests, ...) — see thedekko-orientskill, and use those tools yourself for every follow-up question in this session instead of Grep/Read. - Do not read
.dekko/MAP.mdback into context (it can be large) — prefer the query commands for follow-up questions. - If
$ARGUMENTSincluded--exclude GLOB, mention that the pattern(s) were also persisted to.dekko/.dekkoignore(gitignore syntax) so future baredekko mapruns keep honoring them.
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.
- 26d ago Changed · +3 lines 2b40e17fdc88
- 1mo ago First seen · 37 lines · 20 tokens per session scan A 9b0dacc8e2cf
map is a command published in the GitHub repository aahlijia/dekko (5 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
bug-plan-creator
Deep bug investigation with architectural fix plan generation - works with any executor (loop or swarm).
quick-fix
Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.
debug
Systematic debugging with hypotheses and evidence gathering.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
dead-code-report
Generate dead code findings report with implementation plan. Part of dead-code- family.
simplify-verify
Verify simplification candidates pass all gates. Part of simplify- family.