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/dependency-analyzernpx skills add lis186/SourceAtlas --skill dependency-analyzergit 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.00056 | $0.00385 |
| Opus 5 | $0.00028 | $0.00192 |
| Sonnet 5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
dependency-analyzer 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
Dependency Analyzer
When to Use
Trigger this skill when the user:
- Is planning a framework or SDK upgrade
- Wants to know migration effort for version changes
- Asks about deprecated APIs or breaking changes
- Needs to audit usage of a specific library
- Asks "how much work to upgrade X"
Instructions
- Identify the upgrade path or library to analyze
- Run
/sourceatlas:deps "<upgrade>"with the migration description - Returns deprecated APIs, breaking changes, and migration checklist
Command Formats
- iOS upgrade:
/sourceatlas:deps "iOS 16 → 17" - Android:
/sourceatlas:deps "Android API 35" - React:
/sourceatlas:deps "React 17 → 18" - Python:
/sourceatlas:deps "Python 3.11 → 3.12" - Library audit:
/sourceatlas:deps "kotlinx.coroutines"
What User Gets
- Phase 0 Rule Confirmation (preview before scanning)
- Required Changes: Removable checks, deprecated APIs
- Modernization Opportunities: New features available
- Usage Summary: All API usage with file:line references
- Third-party compatibility
- Migration Checklist with effort estimates
Example Triggers
- "We need to upgrade to iOS 17, how much work?"
- "What breaks if we upgrade React to 18?"
- "Plan the Python 3.12 migration"
- "Check our usage of AFNetworking"
- "How hard is the Swift 6 migration?"
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 · 47 lines · 56 tokens per session scan A 3fccff1b0bb0
dependency-analyzer is a skill published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 385 once invoked, about $0.0003 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…