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.resetgit 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.reset)<a href="https://agentmods.dev/commands/lis186/sourceatlas/atlas.reset"><img src="https://agentmods.dev/badge/commands/lis186/sourceatlas/atlas.reset.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.00006 | $0.00647 |
| Opus 5 | $0.00003 | $0.00324 |
| Sonnet 5 | $0.00001 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade C, and why
atlas.reset scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .sourceatlas/* How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SourceAtlas: Clear Saved Results
Context
Target: $ARGUMENTS (default: all)
Your Task
Help user clear saved analysis results from .sourceatlas/ directory.
Step 1: Check what exists
ls -la .sourceatlas/ 2>/dev/null || echo "No .sourceatlas/ directory found"
Also check subdirectories:
# Count files in each subdirectory
for dir in patterns flows impact deps; do
if [ -d ".sourceatlas/$dir" ]; then
count=$(ls -1 ".sourceatlas/$dir" 2>/dev/null | wc -l)
echo "$dir/: $count files"
fi
done
Step 2: Report findings
List what will be deleted based on target:
- If no argument or "all": list everything
- If specific target (e.g., "patterns"): list only that
Example output:
Found the following saved analyses:
- overview.yaml (2025-12-12)
- patterns/ (3 files)
- history.md (2025-12-11)
Are you sure you want to delete?
Step 3: Wait for confirmation
Ask user to confirm. Do NOT proceed without explicit confirmation.
Acceptable confirmations:
- "yes"
- "ok"
- "confirm"
- "delete"
- "sure"
- etc.
Step 4: Delete if confirmed
Based on target:
# All (default, no argument)
rm -rf .sourceatlas/*
# Specific targets
rm -f .sourceatlas/overview.yaml # for "overview"
rm -rf .sourceatlas/patterns/ # for "patterns"
rm -rf .sourceatlas/flows/ # for "flows"
rm -f .sourceatlas/history.md # for "history"
rm -rf .sourceatlas/impact/ # for "impact"
rm -rf .sourceatlas/deps/ # for "deps"
Step 5: Confirm deletion
✅ Cleared [target or ".sourceatlas/"]
If nothing to clear
.sourceatlas/ directory does not exist or is already empty
Target Reference
| Target | Path | Description |
|---|---|---|
overview |
.sourceatlas/overview.yaml |
Project overview |
patterns |
.sourceatlas/patterns/ |
Pattern analysis |
flows |
.sourceatlas/flows/ |
Flow analysis |
history |
.sourceatlas/history.md |
Temporal analysis |
impact |
.sourceatlas/impact/ |
Impact analysis |
deps |
.sourceatlas/deps/ |
Dependency analysis |
| (no argument) | .sourceatlas/* |
Clear all |
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 · 108 lines · 0 tokens per session scan C b8c5ca2e1257
atlas.reset is a command published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 647 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.