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 nicodiansk/turbocharge --skill atlasgit clone --depth 1 https://github.com/nicodiansk/turbochargeWrote 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/nicodiansk/turbocharge/atlas)<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/atlas"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/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/nicodiansk/turbocharge/atlas"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/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.00049 | $0.01484 |
| Opus 5 | $0.00024 | $0.00742 |
| Sonnet 5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
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 11d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlas — Project Domain Map
Generate or update the semantic domain map for this project.
Announce: "Using atlas to map this project's domain."
The Iron Law
NO ATLAS WITHOUT READING THE CODEBASE FIRST
Do not generate from assumptions or memory. Read the actual code, configs, and docs.
Step 1: Detect Mode
- If ATLAS.md does NOT exist in the project root → Generate mode
- If ATLAS.md exists → Update mode
Step 2: Read the Codebase
Regardless of mode:
- Read project structure (directory listing, key config files)
- Read CLAUDE.md if it exists — understand what's already documented (don't duplicate it)
- Read entry points (main files, CLI entry, API routers, job schedulers)
- Read domain models (data classes, schemas, database models)
- Scan integration configs (env files, connection strings, external service clients)
Step 2b: Read Codemap Index (if available)
If .codemap/.codemap.json exists in the project root:
- Read
.codemap/.codemap.json— it contains a manifest withdirectories(list of indexed paths) andstats(total files, total symbols). - For each directory in the manifest, read
.codemap/<dir>/.codemap.json— each containsfileswith symbol entries (name, type, lines, language). - Use this data to pre-populate:
- Module Map — each directory with its file count and key files
- Key Symbols — pick the 20-30 most important symbols (classes, exported functions) with their
file:line-range
- You still need to fill in the semantic layer manually: Where to Look (intent→file mapping), Entry Points (which files boot the app), Integration Points (external services), Conventions & Gotchas.
This shortcut reduces atlas generation from ~20 tool calls to ~5. If .codemap/ does not exist, skip this step entirely — fall through to the standard codebase scan in Step 2.
Step 3: Generate or Update
Generate Mode (no ATLAS.md)
Create ATLAS.md in the project root following the format in Step 4.
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.
- 11d ago First seen · 159 lines · 49 tokens per session scan A 2e3ecea9661b
atlas is a skill published in the GitHub repository nicodiansk/turbocharge (2 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,484 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
ccs-align
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle cache via atomic grab → append → filter exclude-marks → replace, manage exclude marks, and walk house → project → seat…
design-is
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
smart-explore
Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
wowerpoint
Turn one document into a kawaii NotebookLM slide-deck PDF. Use for "wowerpoint this", "make a deck about ", "turn this report into slides", or any request to render a single document as shareable narrative slides.
standup
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.