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/dsm5e/aso-tracker/releasegit clone --depth 1 https://github.com/dsm5e/aso-trackerWhat 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.00014 | $0.00244 |
| Opus 5 | $0.00007 | $0.00122 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
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 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.
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
Walk through a release for version $ARGUMENTS (e.g. /project:release 2.1.0).
If no version argument is provided, check CHANGELOG.md for the latest version and ask what the new version should be.
Steps:
- Validate — run
python3 validate.py. Stop if any check fails. - Changelog check — confirm CHANGELOG.md has an entry for this version. If not, ask what to add.
- Commit — stage and commit any pending changes with message:
feat: v$ARGUMENTS — <summary from changelog> - Tag — create git tag
v$ARGUMENTS - Push — push commit and tag:
git push && git push --tags - GitHub release — create release from the tag:
gh release create v$ARGUMENTS --title "v$ARGUMENTS" --notes-file -using the changelog entry as notes.
Confirm with the user before each destructive/visible step (commit, push, release).
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 · 19 lines · 14 tokens per session scan A 14b6f7725386
release is a command published in the GitHub repository dsm5e/aso-tracker (134 stars, last pushed 17d ago), licensed MIT. It adds 14 tokens to every session and 244 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.