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/dorayo/orchestrix-skills/map-codebasenpx skills add dorayo/orchestrix-skills --skill map-codebasegit clone --depth 1 https://github.com/dorayo/orchestrix-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/dorayo/orchestrix-skills/map-codebase)<a href="https://agentmods.dev/skills/dorayo/orchestrix-skills/map-codebase"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/map-codebase.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00886 |
| Opus 5 | $0.00018 | $0.00443 |
| Sonnet 5 | $0.00007 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Codebase (Brownfield Entry)
Greenfield runs start from intent; brownfield runs start from SOMEONE ELSE'S decisions. Changing code you haven't mapped produces changes that fight the codebase — wrong layer, wrong convention, duplicated machinery.
Core principle: The map comes from reading code, not from directory names
or the README. A README describes what the project wishes it were; git log
and the source describe what it is.
Process
- Inventory. Layout, manifests (
package.json/pyproject/go.mod…), scripts, CI config, generated/vendored dirs (mark them DO-NOT-EDIT). - Trace one or two REAL flows end to end (guided by
focusif given): entry point → routing/dispatch → business logic → persistence/IO. Read the actual files; record the chain asfile:symbol → file:symbol. This step is what separates a map from a guess. - Extract conventions from evidence — for each, cite the example file you derived it from: naming, module boundaries, error handling style, test location and framework, how config/env is read, commit message style.
- Hazards. Migrations and how they run; generated code and what generates
it; global state; areas with no test coverage; anything
git logshows as churn-heavy (bug-prone) or untouched-for-years (fragile assumptions). - Write back to the
registry/*namespace (physical path fromcore-config.yaml; defaultknowledge/registry/) following the metabolism governance inorchestrate(read-before-write, update-don't-append, facts only):registry/architecture.md— the traced structureregistry/conventions.md— the evidenced conventions Registry holds FACTS about this codebase. Opinions and preferences belong intaste/*, and only via a human correction — not from this skill.
Output: codebase_map
# Codebase map — <repo> @ <commit>
## Shape — <stack, top-level layout, one paragraph>
## Traced flows
- <flow>: entry `a.ts:handler` → `b.ts:service` → `c.ts:repo` → <storage>
## Conventions (evidence-cited)
- <convention> — see <file>
## Hazards
- <hazard> — <why it bites> — <file/dir>
## Where a change like "<focus>" belongs — <layer/files>, following <convention>
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.
- 3d ago First seen · 81 lines · 36 tokens per session scan A cd9152f91c95
map-codebase is a skill published in the GitHub repository dorayo/orchestrix-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 886 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…