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 cathrynlavery/repo-atlas --skill repo-atlasgit clone --depth 1 https://github.com/cathrynlavery/repo-atlasWrote 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/cathrynlavery/repo-atlas/repo-atlas)<a href="https://agentmods.dev/skills/cathrynlavery/repo-atlas/repo-atlas"><img src="https://agentmods.dev/badge/skills/cathrynlavery/repo-atlas/repo-atlas/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/cathrynlavery/repo-atlas/repo-atlas"><img src="https://agentmods.dev/badge/skills/cathrynlavery/repo-atlas/repo-atlas.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.00094 | $0.01335 |
| Opus 5 | $0.00047 | $0.00668 |
| Sonnet 5 | $0.00019 | $0.00267 |
| Haiku 4.5 | $0.00009 | $0.00134 |
Grade A, and why
repo-atlas 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 12d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Atlas
Build an in-repo persistent context system so engineers and LLM agents can understand any codebase quickly with minimal searching.
Hard Constraints
- Do NOT change product/runtime behavior
- No paid/hosted tooling — everything lives in the repo
- Zero or minimal dependencies (Python 3 standard library only)
- All generated content must reflect real repo specifics, not generic filler
Workflow
Phase 1: Reconnaissance
Before writing anything, understand the repo:
- Read the top-level directory structure
- Identify the repo type (app, backend/API, library, monorepo, CLI, infrastructure)
- Identify the primary language(s) and framework(s)
- Find entrypoints, build configs, CI files
- Read 5-10 key files to understand architecture patterns
Phase 2: Run the Generator Script
Copy scripts/generate_atlas.py (bundled with this skill) to the repo at scripts/atlas/generate_atlas.py. Then customize and run it:
- Copy the script to the target repo
- Review and adjust the configuration section at the top:
IGNORE_NAMES— add repo-specific directory names to ignore (exact segment match)TREE_ANNOTATIONS— add short descriptions for key directoriesENTRYPOINT_NAMES— add framework-specific entry filenamesENTRYPOINT_PATH_PATTERNS— add path-based patterns (fnmatch style, e.g.,cmd/*/main.go)ENTRYPOINT_CONTENT_MARKERS— add code markers that identify entry pointsCONVENTIONAL_COMMITS— adjust if repo uses different commit conventionsCHANGELOG_DAYS— change the changelog lookback window (default: 14)
- Run:
python3 scripts/atlas/generate_atlas.py --write
This auto-generates:
docs/atlas/repo-map.md— directory tree + entrypoints + file statsdocs/atlas/08_CHANGELOG_LAST_14_DAYS.md— categorized recent commits
Phase 3: Enhance repo-map.md
After the script generates the skeleton, manually add these sections to repo-map.md:
Router Table — "Where to look for X" (10-15 rows):
## Where to Look for X
| Task | Start Here |
|------|-----------|
| Fix [domain concept] | `path/to/file.ext` |
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.
- 12d ago First seen · 133 lines · 94 tokens per session scan A ae9c2548771c
repo-atlas is a skill published in the GitHub repository cathrynlavery/repo-atlas (51 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,335 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…