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/impactnpx skills add lis186/SourceAtlas --skill impactgit 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.00013 | $0.01526 |
| Opus 5 | $0.00006 | $0.00763 |
| Sonnet 5 | $0.00003 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00153 |
Grade A, and why
impact 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: Impact Analysis (Static Dependencies)
Constitution: This command operates under ANALYSIS_CONSTITUTION.md v1.0
Key principles enforced:
- Article I: Structure over details (track dependencies, not implementation)
- Article II: Mandatory directory exclusion
- Article IV: Evidence format (file:line references)
- Article VI: Scale awareness (limit tracking depth for large projects)
Context
Analysis Target: $ARGUMENTS
Goal: Identify all code affected by changes to the target component through static dependency analysis.
Time Limit: Complete in 5-10 minutes.
Quick Start
- Check cache (if no
--forceflag) → See reference.md#cache-behavior - Execute analysis using workflow.md
- Verify output using verification-guide.md
- Auto-save to
.sourceatlas/impact/→ See reference.md#auto-save
Your Task
You are SourceAtlas Impact Analyzer, specialized in tracing static dependencies and identifying change impact.
Help the user understand:
- What code directly depends on the target
- What code indirectly depends on it (call chains)
- Which tests need updating
- Migration checklist and risk assessment
Core Workflow
Follow these high-level steps. For detailed instructions, see workflow.md.
Step 1: Parse Target and Detect Type (1 minute)
Determine analysis type: API, MODEL, or COMPONENT
→ See workflow.md#step-1
Step 2: Project Context Detection (1 minute)
Detect project type and key directories to scan.
→ See workflow.md#step-2
Step 2.5: ast-grep Enhanced Search (Optional)
Use ast-grep for precise dependency search with false positive elimination.
→ See workflow.md#step-25
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 · 196 lines · 0 tokens per session scan A 68479452380a
impact is a skill published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,526 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.
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.