Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Eigenwise/eigenwise-toolshed/plugin install codebase-mapperWrote 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/skills/eigenwise/eigenwise-toolshed/map-codebase)<a href="https://agentmods.dev/skills/eigenwise/eigenwise-toolshed/map-codebase"><img src="https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/map-codebase/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/skills/eigenwise/eigenwise-toolshed/map-codebase"><img src="https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/map-codebase.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.00040 | $0.03946 |
| Opus 5.5 | $0.00016 | $0.01578 |
| Sonnet 5.5 | $0.00008 | $0.00789 |
| Haiku 4.5 | $0.00004 | $0.00395 |
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 1mo 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Codebase
Generate a codebase map as a collection of atomic documents in .claude/.codebase-info/. Each
document covers one aspect of the project, so the map stays easy to read, update, and navigate. The
map is written for the next Claude session (and the next human): it is grounding context, not
marketing.
Loading is automatic and you don't have to wire anything up: this plugin ships a SessionStart
hook that injects the map at the start of each session, so Claude starts oriented and keeps
consulting and updating it as work goes on. Never edit CLAUDE.md. The hook is the only loading
mechanism; leave CLAUDE.md alone. Your job is just to write the docs in .claude/.codebase-info/.
Output
.claude/.codebase-info/
├── INDEX.md # Navigation hub + how-to-use; the hook injects this at session start
├── architecture.md # System overview, components, boundaries, data flow
├── tech-landscape.md # Languages, frameworks, runtimes, infra, source-of-truth files
├── directory-structure.md # Annotated folder tree
├── entry-points.md # Where execution starts (routes, CLIs, jobs, main files)
├── modules.md # Key modules/packages: purpose, deps, exports
├── communication.md # APIs, events, queues, external integrations (if applicable)
├── database.md # Schema, relationships, migrations (if applicable)
├── dependencies.md # Categorized packages (if applicable)
├── patterns.md # Recurring patterns, error handling, testing, config
├── coding-style.md # Conventions derived from linters + existing code
├── docker.md # Containers / local dev environment (if applicable)
├── onboarding.md # Quick start + common tasks
└── .map-state.json # Machine state (last-mapped commit + date) for staleness checks
This list is a menu, not a checklist. Create only the documents that earn their place in this codebase, and feel free to go beyond the list when a project has a major aspect the standard docs do not cover. Two directions:
What ships with it
2 files 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.
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.
- 1mo ago Changed · +10 lines dcc0d87a0063
- 1mo ago First seen · 266 lines · 40 tokens per session scan A 8d90d95146d1
map-codebase is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (280 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 3,946 once invoked, about $0.0002 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-30.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
porters-five-forces
Perform Porter's Five Forces analysis — competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants. Use when analyzing industry dynamics, assessing competitive forces, or evaluating market attractiveness.