A compact map of the important symbols in a codebase, such as functions and classes. A codebase is the collection of source files that make up a software project.

Use it when joining a project, preparing a refactor or deep review, or giving other agents a focused overview of the repository.

It gives a quick view of how an unfamiliar or large project is structured without reading every file. This saves context and points to the files most worth inspecting.

repo-map — Skill for Claude Code by AnastasiyaW

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.

Any agent

npx skills add AnastasiyaW/codex-claude-code-config --skill repo-map

Clone the repo

git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config

Made for: Claude Code.

Or install claude-code-config, the plugin that ships this one along with the rest of its 57 skills, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/repo-map/github.svg)](https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/repo-map)

Your own site

<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/repo-map"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/repo-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/repo-map"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/repo-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 145 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,463 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.1	$0.00145	$0.01463
Opus 5	$0.00072	$0.00732
Sonnet 5	$0.00029	$0.00293
Haiku 4.5	$0.00015	$0.00146

Measured yesterday against content hash 772f54c2730e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

repo-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 yesterday.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/repo_map.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/development/repo-map/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

repo-map

Produces a ranked list of the structurally-important symbol definitions in a codebase, capped to a token budget. The point: instead of dumping whole files (wasteful, blows the context window), get a cheap "skeleton" of the repo — the functions/classes everything else depends on — and read full files only where it matters.

This is our zero-dependency port of Aider's repo-map.

When to use

Onboarding to an unfamiliar or large codebase — get the lay of the land first.
Before a refactor / deep-review / workflow-orchestration fan-out — feed each subagent the map so it knows the important entry points without re-scanning.
JIT context (principle 07 / practice_context_engineering) — load the map, not the files.
Anytime the instinct is "let me read 20 files to understand this" → run this first.

Usage

python scripts/repo_map.py [ROOT] [--budget-tokens N] [--top N] [--json] [--no-signature] [--max-files N]

ROOT — repo root (default: cwd). If it's a git repo, only tracked files are scanned (honors .gitignore); otherwise a filtered directory walk is used.
--budget-tokens (default 1024) — stop emitting once ~this many tokens are used (≈4 chars/token heuristic). Use 256–512 for a quick orientation, 2048+ for depth.
--top N — hard cap on symbols before the budget applies.
--json — machine-readable output (for piping into a workflow / another agent).
--no-signature — emit path:line: name instead of the full signature line.

JSON distinguishes symbols_extracted_total (before --top), symbols_ranked_after_top (after that cap), and symbols_emitted (after the token budget). The legacy symbols_total key retains its post---top meaning for compatibility. None is a semantic coverage guarantee: extraction is regex-based and --max-files can limit input. Never diagnose parser coverage from a capped map.

Typical recipes

# Quick orientation in a new repo
python scripts/repo_map.py . --budget-tokens 512

# Feed a fan-out: JSON map of the most important 40 symbols
python scripts/repo_map.py /path/to/repo --top 40 --json > repo_map.json

# Focus a subdirectory (a single layer/service)
python scripts/repo_map.py /path/to/repo/services/auth --budget-tokens 800

Read the full file on GitHub · 104 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/repo_map.py 14 KB runs code

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.

yesterday Changed · +7 lines · -3 tokens per session 772f54c2730e
9d ago First seen · 97 lines · 148 tokens per session scan A 986169bba183

Subscribe to this mod's changes

repo-map is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed today), licensed MIT. It adds 145 tokens to every session and 1,463 once invoked, about $0.0007 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.

Claude Code LLM Planning ai-agents claude machine-learning prompt-engineering

repo-map

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

repo-map

When to use

Usage

Typical recipes

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

ai-content-filter

ai-engineer

ai-product-manager

embedding-architect

eval-harness

feature-engineer