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/lis186/sourceatlas/overviewnpx skills add lis186/SourceAtlas --skill overviewgit clone --depth 1 https://github.com/lis186/SourceAtlasWhat 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.00020 | $0.02644 |
| Opus 5 | $0.00010 | $0.01322 |
| Sonnet 5 | $0.00004 | $0.00529 |
| Haiku 4.5 | $0.00002 | $0.00264 |
Grade A, and why
overview 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.
How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: Project Overview (Stage 0 Fingerprint)
Constitution: ANALYSIS_CONSTITUTION.md v1.0
Context
Arguments: ${ARGUMENTS:-.}
Goal: Generate project fingerprint by scanning <5% of files to achieve 70-80% understanding in 10-15 minutes.
Auto-Save: Results automatically saved to .sourceatlas/overview.yaml (or subdirectory-specific path)
Time Limit: 10-15 minutes (typically 0-5 minutes)
Cache Check (Highest Priority)
If --force is NOT in arguments, check cache first:
-
Calculate cache path:
- No path argument or
.:.sourceatlas/overview.yaml - With path (e.g.,
src/api):.sourceatlas/overview-src-api.yaml
- No path argument or
-
Check if cache exists:
ls -la .sourceatlas/overview.yaml 2>/dev/null -
If cache exists:
- Calculate days since modification
- Use Read tool to read cache
- Output:
📁 Loading cache: .sourceatlas/overview.yaml (N days ago) 💡 Add --force to re-analyze - If over 30 days: Show warning
- Output cache content
- End, do not execute analysis
-
If cache does not exist: Continue with analysis
If --force is in arguments: Skip cache, execute analysis
Your Task
Execute Stage 0 Analysis Only - generate project fingerprint using information theory principles.
Information Theory Approach:
- High-entropy files contain disproportionate information
- Scan priority: Documentation → Configuration → Models → Entry Points → Tests
- Scale-aware: TINY/SMALL/MEDIUM/LARGE/VERY_LARGE projects need different approaches
Core Workflow
Execute these phases in order. See workflow.md for complete details.
Phase 1: Project Detection & Scale-Aware Planning (2-3 minutes)
Purpose: Detect project type, count files, determine scale, set scan limits.
Execute detection:
# Try helper script first (recommended)
if [ -f ~/.claude/scripts/atlas/detect-project.sh ]; then
bash ~/.claude/scripts/atlas/detect-project.sh ${ARGUMENTS:-.}
elif [ -f scripts/atlas/detect-project.sh ]; then
bash scripts/atlas/detect-project.sh ${ARGUMENTS:-.}
else
echo "Warning: detect-project.sh not found, using manual detection"
fi
What ships with it
4 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.
- 2d ago First seen · 320 lines · 20 tokens per session scan A a5b360727436
overview is a skill published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 2,644 once invoked, about $0.0001 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.
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…