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/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/map-codebase)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/map-codebase"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/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/rules/danielvm-git/bigpowers/map-codebase"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/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.00062 | $0.00788 |
| Opus 5.5 | $0.00025 | $0.00315 |
| Sonnet 5.5 | $0.00012 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Codebase
Perform a deep architectural and structural analysis of the codebase. Unlike survey-context which identifies "where we are", map-codebase identifies "what we are dealing with" and "how things are done".
Use this vs survey-context:
map-codebaseBUILDS the tech-stack doc by scanning the codebase from scratch.survey-contextREADS existing specs/tech-architecture docs without re-deriving them. Runmap-codebasewhenspecs/tech-architecture/tech-stack.mddoesn't exist yet; runsurvey-contextwhen it does.
HARD GATE — Cold analysis only. Do NOT assume architectural patterns without reading the code. If the codebase structure surprises you, call out the delta.
Process
1. Identify Core Stack & Dependencies
- Scan
package.json,Cargo.toml,requirements.txt, etc. - Identify primary framework, runtime, and critical libraries (ORM, Auth, State, UI).
- Note version constraints and any deprecated or unusual dependencies.
2. Map High-Level Architecture
- Identify the entry points (CLI, Web, API).
- Map the primary data flow (e.g., Controller → Service → Repository).
- Identify where business logic lives vs. where I/O lives.
- Look for established patterns (e.g., hexagonal, layered, feature-folders).
3. Analyze "Gray Areas" (The "How")
Search for patterns and anti-patterns in these categories:
- Error Handling: Are exceptions caught early or bubbled? Is there a global error handler? Are error messages structured?
- API Shapes: Is it REST, GraphQL, or RPC? What is the casing (camelCase, snake_case)? How are responses structured?
- Type Safety: Is it strictly typed? Are there many
anyorunsafeblocks? Are interfaces used for DIP? - Observability: Is there structured logging? Are there health checks? Where do logs go?
- Testing: What is the test coverage strategy? Are mocks used? Where do tests live?
4. Identify Planning "Signals"
Look for signals that will influence upcoming plans:
- Consistency Gaps: "Half the project uses async/await, the other half uses Promises."
- Debt Hotspots: "The
AuthManageris 1500 lines and handles both JWT and session logic." - Integration Points: "We need to talk to the Stripe API, but there's no wrapper yet."
- Conventions: "The team always uses functional components over classes."
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 First seen · 71 lines · 62 tokens per session scan A e91bf5f52541
map-codebase is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 62 tokens to every session and 788 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
general
API design standards — treat the API as a consumer-facing contract. Apply when designing, reviewing, or changing HTTP endpoints, routes, controllers, request/response payloads, and API resources.
00-project-rules
ContextOS core project rules and role orchestration.
vue
Rules for Vue (2 and 3) single-file components.
node
ContextOS rules for node.