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/depsnpx skills add lis186/SourceAtlas --skill depsgit 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.00011 | $0.02245 |
| Opus 5 | $0.00005 | $0.01123 |
| Sonnet 5 | $0.00002 | $0.00449 |
| Haiku 4.5 | $0.00001 | $0.00225 |
Grade A, and why
deps 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 3d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: Dependencies
Constitution: ANALYSIS_CONSTITUTION.md v1.1
Context
Target: $ARGUMENTS (library name, version upgrade, or iOS minimum version) Goal: Analyze dependency usage and provide upgrade guidance Time Limit: 5-15 minutes
Quick Start
- Check cache (skip if
--forceflag present) - Detect version from manifest files (package.json, Podfile, etc.)
- Search for upgrade rules using WebSearch (if version upgrade)
- Find all usage points using grep/Glob
- Categorize usage by API type
- Generate YAML report following output-template.md
- Verify output using verification-guide.md
- Auto-save to
.sourceatlas/deps/
Your Task
You are analyzing dependency usage to help users understand:
- Current state: Which version is installed, where it's used
- Upgrade impact: What needs to change for version upgrades
- Migration path: Step-by-step upgrade checklist
- Risk assessment: How complex is the upgrade
Upgrade Types You Handle
| Input Pattern | Type | Focus |
|---|---|---|
iOS 17, iOS 16 → 17 |
iOS Minimum Version Upgrade | Removable #available, deprecated APIs, new opportunities |
iOS SDK 26, Xcode 16 |
SDK/Compiler Upgrade | Compilation warnings, Swift version, new syntax |
react 17 → 18, pandas 1.x → 2.x |
Major Version Upgrade | Breaking changes, deprecated APIs, new patterns |
react, pandas (no version) |
Usage Inventory | List usage points only |
Core Workflow
Execute these phases in order. See workflow.md for complete details.
Phase 0: Rule Confirmation (1-2 minutes)
Purpose: Identify upgrade type and confirm analysis rules with user before proceeding.
Steps:
- Detect upgrade type from
$ARGUMENTS - Generate rules preview (what to check, where to search)
- Use
AskUserQuestionto confirm rules
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.
- 3d ago First seen · 295 lines · 0 tokens per session scan A c68fb2cab691
deps is a skill published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,245 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…