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 MarcinHamiga/code-indexing-mcp --skill codebase-explorationgit clone --depth 1 https://github.com/MarcinHamiga/code-indexing-mcpWrote 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/marcinhamiga/code-indexing-mcp/codebase-exploration)<a href="https://agentmods.dev/skills/marcinhamiga/code-indexing-mcp/codebase-exploration"><img src="https://agentmods.dev/badge/skills/marcinhamiga/code-indexing-mcp/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/marcinhamiga/code-indexing-mcp/codebase-exploration"><img src="https://agentmods.dev/badge/skills/marcinhamiga/code-indexing-mcp/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.00041 | $0.00558 |
| Opus 5.5 | $0.00016 | $0.00223 |
| Sonnet 5.5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
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 2mo 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
You are exploring a codebase to answer: $question. If the question is missing or too vague to search against, ask the user with the AskUserQuestion tool before starting.
The core rule of this skill: narrow down with the index first; read files last. Do not fall back to Grep/Glob/Read for code exploration while the code-indexing-mcp tools are available.
1. Ensure the index is ready
- Call
mcp__code-indexing-mcp__project_statusfor the target project. If the project is unknown, callmcp__code-indexing-mcp__list_projectsand, if needed,mcp__code-indexing-mcp__init_project. - If the index is missing or stale relative to the files in question, call
mcp__code-indexing-mcp__index_projectfirst. Tell the user if indexing will take a moment.
2. Narrow down semantically
mcp__code-indexing-mcp__search_code— issue several targeted natural-language queries derived from the question (the concept, the mechanism, the data it touches). Not one broad query.mcp__code-indexing-mcp__find_symbol— once you have a concrete function/class/module name, jump straight to its definitions and references instead of more searching.
Keep a shortlist of candidate files and symbols; discard paths the results rule out.
3. Outline before reading
mcp__code-indexing-mcp__file_outline— get each candidate file's structure and decide which symbols matter. Never dump a whole file just to find one thing.
4. Read only what matters
mcp__code-indexing-mcp__get_chunk— pull the full body of the specific chunks that answer the question.- Use Read/Grep only for content the index does not cover (non-code files, unindexed paths, exact literal matches semantic search cannot express) — and say so when you do.
5. Answer
Answer the question with path:line references for every claim, the shortest explanation that is complete, and an explicit note of anything the index could not cover so the user knows what was not verified.
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.
- 2mo ago First seen · 38 lines · 41 tokens per session scan A 72e30a4ae1ad
codebase-exploration is a skill published in the GitHub repository MarcinHamiga/code-indexing-mcp (0 stars, last pushed 25d ago), licensed MIT. It adds 41 tokens to every session and 558 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…