What is map-codebase?

A command that examines an existing software repository and creates baseline documentation in a Memory Bank, including its architecture, components, workflows, and testing. It records what the code shows rather than planning new work.

Use it to document a brownfield repository before making changes, by reviewing areas such as tooling, backend, frontend, data, and tests. It can also identify contradictions and ask for the product changes that should guide the next step.

It gives developers a shared map of an unfamiliar codebase and separates confirmed facts from assumptions or unresolved questions. It also prevents generating task roadmaps when no product requirements document exists.

map-codebase — Command by mrvladd-d

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/mrvladd-d/memobank/map-codebase

Clone the repo

git clone --depth 1 https://github.com/mrvladd-d/memobank

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 585 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.

Model	Per session	Once invoked
Fable 5	$0.00019	$0.00585
Opus 5	$0.00010	$0.00293
Sonnet 5	$0.00004	$0.00117
Haiku 4.5	$0.00002	$0.00059

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

Security

Grade A, and why

map-codebase 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.

skills/_shared/references/commands/map-codebase.md · 55 lines

What it actually says

/map-codebase — Brownfield mapping

Создай .tasks/TASK-MB-MAP/.
Запусти сабагентов по зонам (до 5–7 параллельно):

tooling/CI
backend
frontend
data
tests

Каждый сабагент:

smart calling (глобы должны матчиться)
пишет отчёт в .tasks/TASK-MB-MAP/...

Синтезируй .memory-bank/ по чеклисту:

product
architecture (C4)
spec-index / glossary / invariants (если есть достаточно evidence для явного normative routing)
runbooks
contracts
states (если lifecycle/state rules очевидны из кода, workflow или тестов)
testing
index

PRD-less rule (non-negotiable): если нет prd.md, запрещено генерировать roadmap сущности:

.memory-bank/epics/*

.memory-bank/features/*

.memory-bank/tasks/*.task.json task records

.memory-bank/tasks/index.json task links

Маппинг = as-is документация по evidence, а не планирование.

Сделай fan-in:

сведи отчёты сабагентов
устрани противоречия (или запиши как “needs verification”)
раздели facts vs inferences

Попроси у пользователя PRD delta (что хотим изменить).
- Если delta уже оформлена как PRD — /constitution, если principles не ratified/partial, затем /write-prd --delta, /spec-init, /prd, /spec-design, /spec-improve FT-<NNN> и /prd-to-tasks FT-<NNN>.
- Если delta ясна, но PRD нет — сначала /brief, затем /constitution, если principles не ratified/partial, затем /write-prd, /spec-init, /prd, /spec-design, /spec-improve FT-<NNN> и /prd-to-tasks FT-<NNN>.
- Если delta сырая / направление нестабильно — сначала /analysis или /brainstorm.
- Не переходи напрямую к /prd-to-tasks; для planning delta сначала нужен /write-prd, /spec-init, /prd, /spec-design и /spec-improve FT-<NNN>.
Запусти /review.

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.

2d ago First seen · 55 lines · 19 tokens per session scan A 6e28e4265dbc

Subscribe to this mod's changes

map-codebase is a command published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 585 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.

Frontend Memory and context Testing

map-codebase

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/map-codebase — Brownfield mapping

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement