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.overviewgit 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.overview)<a href="https://agentmods.dev/commands/lis186/sourceatlas/atlas.overview"><img src="https://agentmods.dev/badge/commands/lis186/sourceatlas/atlas.overview.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.00018 | $0.04889 |
| Opus 5 | $0.00009 | $0.02445 |
| Sonnet 5 | $0.00004 | $0.00978 |
| Haiku 4.5 | $0.00002 | $0.00489 |
Grade A, and why
atlas.overview 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 4d 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 — 547 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: Project Overview (Stage 0 Fingerprint)
Constitution: This command operates under ANALYSIS_CONSTITUTION.md v1.0
Key principles enforced:
- Article I: High-entropy priority, scan ratio limits
- Article II: Mandatory directory exclusions
- Article III: Hypothesis count limits, required elements
- Article IV: Evidence format requirements
Context
Arguments: ${ARGUMENTS:-.}
Save Mode: Check if --save is in arguments. If present:
- Remove
--savefrom path argument - After analysis, save YAML to
.sourceatlas/overview.yaml - Create
.sourceatlas/directory if needed
Analysis Target: Parse from arguments (default: current directory)
Goal: Generate a comprehensive project fingerprint by scanning <5% of files to achieve 70-80% understanding in 10-15 minutes.
Cache Check (Highest Priority)
If --force is NOT in arguments, check cache first:
-
Calculate cache path:
- No path argument or
.:.sourceatlas/overview.yaml - With path argument (e.g.,
src/api):.sourceatlas/overview-src-api.yaml(slashes to-)
- No path argument or
-
Check if cache exists:
ls -la .sourceatlas/overview.yaml 2>/dev/null -
If cache exists:
- Read modification date from
lsoutput - Calculate days since modification
- Use Read tool to read cache content
- Output:
📁 Loading cache: .sourceatlas/overview.yaml (N days ago) 💡 Add --force to re-analyze - If over 30 days, also show:
⚠️ Cache is over 30 days old, recommend re-analysis - Then output:
--- [cache content] - End, do not execute subsequent analysis
- Read modification date from
-
If cache does not exist: Continue with the analysis flow below
If --force is in arguments: Skip cache check, execute analysis directly
Your Task
Execute Stage 0 Analysis Only - generate a project overview using information theory principles.
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.
- 4d ago First seen · 547 lines · 0 tokens per session scan A 7528eed135e1
atlas.overview is a command published in the GitHub repository lis186/SourceAtlas (48 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 4,889 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.