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/ssbun/csl-agent-kit/repo-mapnpx skills add SSBun/csl-agent-kit --skill repo-mapgit clone --depth 1 https://github.com/SSBun/csl-agent-kitWrote 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/ssbun/csl-agent-kit/repo-map)<a href="https://agentmods.dev/skills/ssbun/csl-agent-kit/repo-map"><img src="https://agentmods.dev/badge/skills/ssbun/csl-agent-kit/repo-map.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.1 | $0.00073 | $0.00597 |
| Opus 5 | $0.00036 | $0.00298 |
| Sonnet 5 | $0.00015 | $0.00119 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
repo-map 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 6d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Map
Build a compact, objective structure map and shared glossary before editing or deep-diving. This is quick orientation work, not a durable systematic analysis, full audit, or recommendation document.
Output Contract
Respond in chat unless the user asks for a file. If saving, write docs/analysis/repo-map.md in the target repo.
Include:
- Component summary: 1-3 sentences about what the scoped component does.
- Project glossary: 8-20 repo-specific domain/code terms, with source paths.
- Working map: file structure, modules, key types, and core data/control flows.
Exclude subjective opinions, risks, recommendations, confidence ratings, open questions, and audit findings.
Workflow
- Resolve git roots first. If the working folder contains multiple child repos, map them separately.
- Define scope from the user's feature, bug, file, symbol, or module. Do not read every file by default.
- Inventory manifests, READMEs, tests, entry points, and domain-heavy filenames with
rg --files. - Use CodeGraph when available for callers, callees, impact, and symbol lookup. Confirm important conclusions by reading files.
- Identify boundary types: app roots, controllers, services, stores, reducers, models, protocols, dependency containers, API clients, persistence layers, and coordinators.
- Build a small glossary from project usage, marking inferred terms explicitly.
- Trace relationships from entry points to domain logic and persistence/API/UI boundaries.
- Stop once the map is useful for the next task.
References
Read references/repo-map-workflow.md for detailed root detection, CodeGraph, glossary, and relationship tracing rules.
Choose the closest format guide:
references/repo-map-web-example.md- web frontend.references/repo-map-backend-example.md- backend service or worker.references/repo-map-apple-example.md- iOS, macOS, SwiftUI, UIKit, AppKit, XCTest.references/repo-map-android-example.md- Android, Gradle, Kotlin, Java, Compose, XML layouts.
What ships with it
5 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.
- 6d ago First seen · 52 lines · 73 tokens per session scan A 5e55de3f875c
repo-map is a skill published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 597 once invoked, about $0.0004 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.
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…