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.
git 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/pre-release)<a href="https://agentmods.dev/commands/lis186/sourceatlas/pre-release"><img src="https://agentmods.dev/badge/commands/lis186/sourceatlas/pre-release/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/commands/lis186/sourceatlas/pre-release"><img src="https://agentmods.dev/badge/commands/lis186/sourceatlas/pre-release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00006 | $0.00357 |
| Opus 5.5 | $0.00002 | $0.00143 |
| Sonnet 5.5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
pre-release 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.
What it actually says
Pre-Release Checklist
Trigger: Before asking "Should we update the version?"
Checklist (11 items)
| # | Item | Location |
|---|---|---|
| 1 | README version badge | README.md, README.zh-TW.md |
| 2 | CLAUDE.md version | CLAUDE.md header |
| 3 | Plugin version | plugin/.claude-plugin/plugin.json |
| 4 | Marketplace version | .claude-plugin/marketplace.json |
| 5 | Plugin CHANGELOG | plugin/CHANGELOG.md |
| 6 | Dev history | dev-notes/HISTORY.md |
| 7 | Implementation notes | dev-notes/YYYY-MM/YYYY-MM-DD-*.md |
| 8 | Command files sync | .claude/commands/ ↔ plugin/commands/ |
| 9 | Command footers | Version in command files |
| 10 | USAGE_GUIDE footers | USAGE_GUIDE.md, USAGE_GUIDE.zh-TW.md |
| 11 | New scripts | scripts/atlas/*.sh executable |
Flow
1. Feature implementation complete
2. Execute all 11 checks
3. Fix any missing items
4. Ask user: "Update version to vX.Y.Z?"
5. Execute only after confirmation
Version Rules
- PATCH (x.y.Z): Bug fixes, minor improvements
- MINOR (x.Y.0): New features, new commands
- MAJOR (X.0.0): Breaking changes
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 · 40 lines · 6 tokens per session scan A 1b6a82ec4e1b
pre-release is a command published in the GitHub repository lis186/SourceAtlas (48 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 357 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 commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.