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/listnpx skills add lis186/SourceAtlas --skill listgit 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.00008 | $0.00808 |
| Opus 5 | $0.00004 | $0.00404 |
| Sonnet 5 | $0.00002 | $0.00162 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
list 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: List Saved Results
Your Task
List all saved analysis results in the .sourceatlas/ directory.
Step 1: Check directory exists
ls -la .sourceatlas/ 2>/dev/null || echo "NOT_FOUND"
If output contains NOT_FOUND or directory is empty:
📁 No saved analyses yet
Use the `--save` parameter to save analysis results:
- `/sourceatlas:overview --save`
- `/sourceatlas:pattern "api" --save`
- `/sourceatlas:history --save`
End.
Step 2: List all files with details
find .sourceatlas -type f -exec ls -lh {} \; 2>/dev/null | sort
Step 3: Format output
Format results into a table, calculate days since modification, and mark expired status (>30 days):
📁 .sourceatlas/ saved analyses:
| Type | File | Size | Modified | Status |
|------|------|------|----------|--------|
| overview | overview.yaml | 2.3 KB | 3 days ago | ✅ |
| pattern | patterns/api.md | 1.5 KB | 45 days ago | ⚠️ |
| pattern | patterns/repository.md | 2.1 KB | 5 days ago | ✅ |
| history | history.md | 4.2 KB | 60 days ago | ⚠️ |
| flow | flows/checkout.md | 3.1 KB | 2 days ago | ✅ |
| impact | impact/user-model.md | 1.8 KB | 4 days ago | ✅ |
| deps | deps/react.md | 2.5 KB | 6 days ago | ✅ |
📊 Stats: 7 cached, 2 expired (>30 days)
💡 Tips:
- Clear cache: `/sourceatlas:reset`
- Clear specific type: `/sourceatlas:reset patterns`
Step 4: List expired items with refresh commands
If there are expired items (>30 days), output copyable re-analysis commands:
⚠️ Expired items (recommend re-analysis):
| File | Days | Re-analyze Command |
|------|------|-------------------|
| patterns/api.md | 45 days | `/sourceatlas:pattern "api" --force --save` |
| history.md | 60 days | `/sourceatlas:history --force --save` |
💡 Copy the commands above to re-analyze
Command generation rules:
| Type | Command Format |
|---|---|
| overview | /sourceatlas:overview --force --save |
| overview-{dir} | /sourceatlas:overview {dir} --force --save |
| patterns/{name}.md | /sourceatlas:pattern "{name}" --force --save |
| history.md | /sourceatlas:history --force --save |
| flows/{name}.md | /sourceatlas:flow "{name}" --force --save |
| impact/{name}.md | /sourceatlas:impact "{name}" --force --save |
| deps/{name}.md | /sourceatlas:deps "{name}" --force --save |
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 · 104 lines · 8 tokens per session scan A e8fe067062d5
list is a skill published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 808 once invoked, about $0.0000 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.