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 skills/bahdotsh/indxr/explore-codebase-indexnpx skills add bahdotsh/indxr --skill explore-codebase-indexgit clone --depth 1 https://github.com/bahdotsh/indxrWhat 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.00067 | $0.00477 |
| Opus 5 | $0.00034 | $0.00238 |
| Sonnet 5 | $0.00013 | $0.00095 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
explore-codebase-index 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 2d 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
Explore codebase via INDEX.md
When to use
Apply this skill when exploring this repository and the user (or task) needs a structural picture: files, functions, types, classes, and imports across the project.
Instructions
-
Start with the index — Read
.cursor/INDEX.mdearly. It aggregates what would otherwise require many file opens: tree layout, per-file summaries, declarations, and import relationships (generated from the project indexer). -
Use it to route next steps — Pick files and symbols from the index, then open only those regions (e.g. via
read_source, symbol search, or the Read tool for edits). Avoid reading large unrelated areas when the index already answers “what lives where.” -
If the index looks stale — Timestamps and counts appear at the top of
INDEX.md. After substantial code changes, the maintainer may regenerate it (see project guidance such asregenerate_index/ indexer docs in-repo). If sections clearly mismatch the tree on disk, say so briefly and fall back to directory listing plus targeted reads.
Relationship to other tooling
Project rules may require indxr MCP tools for surgical queries. INDEX.md is the offline, whole-repo structural digest; MCP tools are ideal for precise symbol lookup and line-scoped reads. Use both: index for orientation and breadth, MCP (or direct reads) for depth on chosen symbols.
Examples
User: “Where is Rust query logic for TypeScript?”
- Open
.cursor/INDEX.md, find the directory tree and declaration sections forsrc/parser/queries/. - Note
typescript.rs(and related modules), then read only those files or the relevant symbols.
User: “What does the MCP server expose?”
- Scan
INDEX.mdformcp,src/mcp.rs, and linked declarations. - Drill into the named functions/types from there.
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.
- 2d ago First seen · 35 lines · 67 tokens per session scan A e74864b5b602
explore-codebase-index is a skill published in the GitHub repository bahdotsh/indxr (72 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 477 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
langbot-space-ops
Browse and search the LangBot Space marketplaces (plugins, MCP servers, skills) through the Space MCP server. Use when an AI agent needs to discover LangBot extensions on space.langbot.app over MCP. Covers the /mcp endpoint, Personal Access Token (PAT) auth, the tool surface, and client configuration. Triggers on…
ocx
Drive a running opencodex (ocx) proxy from the CLI — account pools, provider routing, model catalog, usage and cost attribution, request logs, access keys, storage cleanup, and the management API. Use when a task involves controlling or inspecting an opencodex proxy rather than editing the opencodex codebase.…
openai-knowledge
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available…
opik-external-integrations
Build or update an Opik integration that lives OUTSIDE this repo — a standalone opik- package (e.g. opik-openclaw, opik-claude-code-plugin) or Opik support contributed into a third-party project (e.g. LiteLLM, Dify). Use ONLY when the user names an external repository or external package as the target; for…
create-atomic-tool
Build a BaseTool[InSchema, OutSchema] subclass — input/output schemas, BaseToolConfig, run() (and optional runasync()), env-driven secrets, typed failure outputs. Use when the user asks to "add a tool", "create a tool", "wrap an API as a tool", "build a BaseTool", "make a calculator/search/weather tool", or runs…