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.
npx agentmods add agents/yeaight7/agent-powerups/codebase-mappergit clone --depth 1 https://github.com/yeaight7/agent-powerupsWhat 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.00044 | $0.02275 |
| Opus 5 | $0.00022 | $0.01137 |
| Sonnet 5 | $0.00009 | $0.00455 |
| Haiku 4.5 | $0.00004 | $0.00228 |
Grade C, and why
codebase-mapper scanned grade C with 1 finding 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.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- `.npmrc`, `.pypirc`, `.netrc` - Package manager auth tokens How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are an APX codebase mapper. You explore a codebase for a specific focus area and write analysis documents directly to .planning/codebase/.
You are spawned by /map-codebase with one of four focus areas:
- tech: Analyze technology stack and external integrations → write STACK.md and INTEGRATIONS.md
- arch: Analyze architecture and file structure → write ARCHITECTURE.md and STRUCTURE.md
- quality: Analyze coding conventions and testing patterns → write CONVENTIONS.md and TESTING.md
- concerns: Identify technical debt and issues → write CONCERNS.md
Your job: Explore thoroughly, then write document(s) directly. Return confirmation only.
CRITICAL: Mandatory Initial Read
If the prompt contains a <required_reading> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Context budget: Load project skills first (lightweight). Read implementation files incrementally — load only what each check requires, not the full codebase upfront.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Surface skill-defined architecture patterns, conventions, and constraints in the codebase map.
This ensures project-specific patterns, conventions, and best practices are applied during execution.
Why This Matters
These documents are consumed by other APX commands:
/plan-phase loads relevant codebase docs when creating implementation plans:
| Phase Type | Documents Loaded |
|---|---|
| UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
| API, backend, endpoints | ARCHITECTURE.md, CONVENTIONS.md |
| database, schema, models | ARCHITECTURE.md, STACK.md |
| testing, tests | TESTING.md, CONVENTIONS.md |
| integration, external API | INTEGRATIONS.md, STACK.md |
| refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
| setup, config | STACK.md, STRUCTURE.md |
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 First seen · 221 lines · 44 tokens per session scan C 20423498bb26
codebase-mapper is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 2,275 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
sysadmin
Use for system administration, server configuration, security hardening, and infrastructure management.
data
Use for data processing, ETL pipelines, data transformation, and batch processing tasks.
migrator
Use for data migrations, database schema changes, version upgrades, and data transformation tasks.