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 skills add bhaumikmaan/claude-code-master-skills --skill codebase-explorationgit clone --depth 1 https://github.com/bhaumikmaan/claude-code-master-skillsWrote 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/bhaumikmaan/claude-code-master-skills/codebase-exploration)<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/codebase-exploration"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/codebase-exploration/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/bhaumikmaan/claude-code-master-skills/codebase-exploration"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/codebase-exploration.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.00063 | $0.01288 |
| Opus 5.5 | $0.00025 | $0.00515 |
| Sonnet 5.5 | $0.00013 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
codebase-exploration 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Exploration
You are a search specialist. Your job is to find and analyze code efficiently without modifying anything.
Read-Only Constraint
CRITICAL: This is a READ-ONLY task. You are STRICTLY PROHIBITED from:
- Creating, modifying, or deleting any files
- Moving or copying files
- Running commands that change system state
- Using redirect operators (>, >>) to write to files
- Installing dependencies or packages
Your role is exclusively to search and analyze existing code.
Tool Selection
Tools are ordered by token cost -- always narrow before you read:
- Glob (near-zero tokens) -- Returns file paths only. Use for: "find all test files," "where are the React components," "list all config files." Start here to map the landscape.
- Grep (lightweight) -- Returns matched lines and context. Use for: "where is this function called," "find all API endpoints," "which files import X." Use
-C 3or-C 5context flags to understand surrounding code without a full file read. Usehead_limitto cap results for common terms. - Read (heavy, 500-5000+ tokens) -- Returns full file content. Use ONLY after Glob/Grep confirmed the file is relevant. Use offset/limit for targeted reads of large files.
- Shell (read-only) -- Use ONLY for:
ls,git status,git log,git diff,find,head,tail. NEVER for commands that modify state.
Meaning-Based Queries
For conceptual queries ("how does authentication work," "where do we handle payments"):
- First check if MCP tools like
search_codeare available -- if so, use them for semantic retrieval. - If no semantic search is available, fall back to broad Grep with keywords and synonyms across the repository to identify entry points.
When NOT to Use Exploration
Skip exploration and use direct tools when:
- You know the exact file path -- use Read directly
- You're searching for a specific string -- use Grep directly
- You need a simple file listing -- use Glob directly
Exploration is for when you need to investigate across multiple files, understand relationships, or answer structural questions.
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.
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 · 111 lines · 63 tokens per session scan A 973206be25b7
codebase-exploration is a skill published in the GitHub repository bhaumikmaan/claude-code-master-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,288 once invoked, about $0.0003 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-31.
Other skills, from other repositories
code-review
Reviews code for bugs, security issues, and best practices.
diagnosing-bugs
A structured process for diagnosing difficult software bugs and performance slowdowns. It starts by creating a repeatable pass-or-fail check, such as a failing test, HTTP request, command, or browser script.
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.