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/Eigenwise/eigenwise-toolshedWrote 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/plugins/eigenwise/eigenwise-toolshed/codebase-mapper)<a href="https://agentmods.dev/plugins/eigenwise/eigenwise-toolshed/codebase-mapper"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/codebase-mapper/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/plugins/eigenwise/eigenwise-toolshed/codebase-mapper"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/codebase-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codebase-mapper 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 12d 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
{
"name": "codebase-mapper",
"version": "2.15.10",
"description": "A self-maintaining codebase map: atomic docs Claude loads at the start of each session and keeps in sync as the code changes. Any stack; greenfield or existing.",
"author": {
"name": "Eigenwise",
"email": "[email protected]"
},
"homepage": "https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/codebase-mapper",
"repository": "https://github.com/Eigenwise/eigenwise-toolshed",
"privacyPolicyUrl": "https://github.com/Eigenwise/eigenwise-toolshed/blob/main/plugins/codebase-mapper/PRIVACY.md",
"documentationUrl": "https://eigenwise.github.io/eigenwise-toolshed/getting-started/codebase-mapper/",
"supportUrl": "https://github.com/Eigenwise/eigenwise-toolshed/issues",
"license": "MIT",
"keywords": [
"documentation",
"codebase",
"mapping",
"context",
"grounding",
"onboarding",
"architecture",
"self-maintaining"
]
}
What it installs
The manifest is a name and a version. 2 skills, 5 hooks travel with it, and installing the plugin installs all of them — 78 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 12d ago Changed · +3 lines d3b4aea44f7a
- 1mo ago Changed 284f641638ad
- 1mo ago First seen · 23 lines scan A 0280f608fa58
codebase-mapper is a plugin published in the GitHub repository Eigenwise/eigenwise-toolshed (280 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
context-mode
MCP server that saves 98% of your context window with session continuity. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and automatic state restore across compactions.
mama
Memory-Augmented MCP Assistant - Chat from anywhere, track decisions, never repeat mistakes.
chamnan
Preserves repository architecture, decisions, work state, and reusable engineering context across coding-agent sessions.
second-brain
Agentic workflow with memory and tribal knowledge. Transforms Claude from goldfish to elephant with persistent knowledge across sessions.
product-marketing-context
The PMM brain — builds and maintains /foundation/brain.md, the GTM context file every other plugin in this stack reads before producing output.
cc-meta
Claude Code meta-skills for cross-project synthesis, context compaction, session intelligence, and memory seed template.