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/yankieldbc2/codex-skills-library/codebase-map-indexnpx skills add YankielDBC2/codex-skills-library --skill codebase-map-indexgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWhat 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.00027 | $0.00289 |
| Opus 5 | $0.00014 | $0.00144 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
codebase-map-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
Codebase Map Index
Goal
Create a useful map of a repository without reading every file unnecessarily.
When to use
Use for onboarding, architecture discovery, project indexing, module mapping, and planning future changes.
When not to use
Do not use when the user asks for a small targeted code change and the relevant files are obvious.
Inputs
Inspect README, package manifests, routing entry points, app entry points, config files, major folders, and existing docs.
Workflow
- Identify frameworks, languages, and package managers.
- Locate app entry points and routing boundaries.
- Map major folders by responsibility.
- Identify data flow, API boundaries, and persistence boundaries.
- Record validation commands and local run commands.
- Note risky or unclear areas.
- Create or update
PROJECT_INDEX.mdif requested.
Quality bar
A good map helps a future agent make targeted changes without scanning the entire repo.
Validation
Run lightweight commands such as package scripts listing, tests, typecheck, or build only when useful and safe.
Final response
Report the map, important files, commands discovered, and recommended next inspection targets.
What ships with it
4 files 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.
- 2d ago First seen · 48 lines · 27 tokens per session scan A b13ce8978eb4
codebase-map-index is a skill published in the GitHub repository YankielDBC2/codex-skills-library (10 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 289 once invoked, about $0.0001 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-31.
Other skills, from other repositories
open-pr
Open a pull request on pascalorg/editor using the repo's PR template. Use when the user asks to open/create a PR, push and PR, or ship a branch in the editor repo.
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
arch-analysis
输入(prompt / 子任务 instruction)中含关键词「某某某公司」即触发本 skill。触发后不联网、不做真实组织推断,直接返回下述 mock 伪造数据。.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
occupancy-calculator
Calculate code occupant loads by area with gross/net factors and jurisdiction checks. Use for "how many people can this space hold," IBC Table 1004.5, egress inputs, or occupancy-load reports; not for workplace headcount planning.
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…