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 commands/lis186/sourceatlas/atlas.depsgit clone --depth 1 https://github.com/lis186/SourceAtlasWrote 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/commands/lis186/sourceatlas/atlas.deps)<a href="https://agentmods.dev/commands/lis186/sourceatlas/atlas.deps"><img src="https://agentmods.dev/badge/commands/lis186/sourceatlas/atlas.deps.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00009 | $0.05554 |
| Opus 5 | $0.00005 | $0.02777 |
| Sonnet 5 | $0.00002 | $0.01111 |
| Haiku 4.5 | $0.00001 | $0.00555 |
Grade A, and why
atlas.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 5d 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 — 728 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: Dependency Analysis
Constitution: This command operates under ANALYSIS_CONSTITUTION.md v1.1
Key principles enforced:
- Article IV: Evidence Format Requirements (file:line references)
- Article V: Output Format (YAML)
Context
Arguments: ${ARGUMENTS}
Goal: Analyze how a specific library, framework, or SDK is used in the codebase to facilitate upgrade planning.
Cache Check (Highest Priority)
If --force is NOT in arguments, check cache first:
-
Extract dependency name from
$ARGUMENTS(remove--save,--force) -
Convert to filename: spaces→
-,→→to, lowercase, remove special chars, truncate to 50 chars- Example:
"react"→react.md - Example:
"iOS 16 → 17"→ios-16-to-17.md - Example:
"Python 3.12"→python-3-12.md
- Example:
-
Check cache:
ls -la .sourceatlas/deps/{name}.md 2>/dev/null -
If cache exists:
- Calculate days since creation
- Read cache content with Read tool
- Output:
📁 Loaded from cache: .sourceatlas/deps/{name}.md (N days ago) 💡 To re-analyze, add --force - If older than 30 days, also show:
⚠️ Cache is older than 30 days, recommend re-analysis - Then output:
--- [Cache content] - Stop here, do not proceed with analysis
-
If cache does not exist: Continue with analysis below
If --force is in arguments: Skip cache check, proceed directly to analysis
Your Task
Phase 0: Rule Confirmation
IMPORTANT: Before starting inventory, confirm analysis rules. This ensures results meet user needs.
Step 0.1: Identify Upgrade Type
Based on ${ARGUMENTS}:
| Input Pattern | Type | Rules to Confirm |
|---|---|---|
iOS 17, iOS 16 → 17 |
iOS Minimum Version Upgrade | Removable #available, deprecated APIs, new API opportunities |
iOS SDK 26, Xcode 16 |
SDK/Compiler Upgrade | Compilation warnings, Swift version changes, 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 | Simply list usage points, no upgrade analysis |
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.
- 5d ago First seen · 728 lines · 0 tokens per session scan A 3f48ec2ee119
atlas.deps is a command published in the GitHub repository lis186/SourceAtlas (48 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 5,554 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.