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/onedro1d/dark-factory/codebase-understandingnpx skills add OneDro1d/dark-factory --skill codebase-understandinggit clone --depth 1 https://github.com/OneDro1d/dark-factoryWrote 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/onedro1d/dark-factory/codebase-understanding)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/codebase-understanding"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/codebase-understanding.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.00073 | $0.00435 |
| Opus 5 | $0.00036 | $0.00217 |
| Sonnet 5 | $0.00015 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
codebase-understanding 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 Understanding (read-first, low-token)
Goal: locate the relevant code in the fewest tokens. NEVER scan the whole repo to answer a question the context store already answers.
Order of reading (stop as soon as you have what you need)
.claude/context/SERVICE-MAP.md— which service/db/queue/API owns this area..claude/context/FINDINGS.md— is this already known/solved?.claude/context/DECISIONS.md— is the current behavior intentional?- The ONE relevant
<service>/CLAUDE.md— contracts, key files, gotchas. - The shared-models
CLAUDE.md— only when tracing a routing key / RPC across services. - Source — targeted, by
file:linefrom the above, via Grep/Read. Not whole-file dumps unless necessary.
Cheap search patterns
- Routing key / RPC:
grep -rn "<routing.key>" <service>/then open the dispatcher. - A symbol:
grep -rn "MethodName\|TypeName" <service>/ --exclude-dir={obj,bin}. - A flow: start at the SERVICE-MAP "In → Out" column, follow the routing key to the next consumer.
Output
A short "where it lives" answer: service, file:line, and the one-line role. Do not paste large code blocks — cite locations.
Don't
- Don't re-derive the architecture; it's in SERVICE-MAP/CLAUDE.md.
- Don't read every service. Read the one(s) the map points to.
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 · 30 lines · 73 tokens per session scan A abca92f2cda4
codebase-understanding is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 435 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-09-01.
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…