map

Command that generates a relational map of a software repository, covering files, functions, signatures, and calls. It saves the map in .dekko/MAP.md and .dekko/map.json.

In plain words
What is it for?
Use it to create or refresh a repository map, review its summary, and prepare the codebase for follow-up dekko queries about context or affected code.
Why use it?
It gives a compact overview of the repository's structure and relationships, making it easier to understand a codebase before making changes.

Command

Install

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.

agentmods
npx agentmods add commands/aahlijia/dekko/map
Clone the repo
git clone --depth 1 https://github.com/aahlijia/dekko
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 407 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00407
Opus 5 $0.00010 $0.00204
Sonnet 5 $0.00004 $0.00081
Haiku 4.5 $0.00002 $0.00041

Measured 2d ago against content hash 9b0dacc8e2cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

integrations/claude/commands/map.md · 37 lines

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.

  1. If the output above shows an error, explain the problem to the user and how to fix it. In particular, if the dekko command was not found, tell them to install it with pip install dekko (or uv tool install dekko). Otherwise:
  2. 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.
  3. 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 via dekko query|context|affected or the dekko MCP tools (query_symbol, get_context_pack, outline, workset, impacted_tests, ...) — see the dekko-orient skill.
  4. Do not read .dekko/MAP.md back into context (it can be large) — prefer the query commands for follow-up questions.
  5. If $ARGUMENTS included --exclude GLOB, mention that the pattern(s) were also persisted to .dekko/.dekkoignore (gitignore syntax) so future bare dekko map runs keep honoring them.
Changes

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.

  1. 2d ago First seen · 37 lines · 20 tokens per session scan A 9b0dacc8e2cf

Subscribe to this mod's changes

map is a command published in the GitHub repository aahlijia/dekko (3 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 407 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-31.