Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/lis186/SourceAtlasnpx agentmods add skills/lis186/sourceatlas/depsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/lis186/sourceatlas/deps)<a href="https://agentmods.dev/skills/lis186/sourceatlas/deps"><img src="https://agentmods.dev/badge/skills/lis186/sourceatlas/deps/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lis186/sourceatlas/deps"><img src="https://agentmods.dev/badge/skills/lis186/sourceatlas/deps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
What 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.1 | $0.00011 | $0.02245 |
| Opus 5.5 | $0.00004 | $0.00898 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 295 lines · 0 tokens per session scan A c68fb2cab691
deps is a skill published in the GitHub repository lis186/SourceAtlas (48 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 2,245 once invoked, about $0.0000 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…