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/robofinsystems/robosystems/release-notesgit clone --depth 1 https://github.com/RoboFinSystems/robosystemsWhat 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.01303 |
| Opus 5 | $0.00005 | $0.00651 |
| Sonnet 5 | $0.00002 | $0.00261 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
release-notes 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft curated release notes for an upcoming milestone release, following the convention in .github/release-notes/README.md.
Why this command exists
tag-release.yml generates release bodies from the changes since the last tag. That suits routine releases but reads poorly for milestones, where the story is what the version is. The curated-notes override has non-obvious rules (body-only format, the file must exist at the tagged ref), and release notes are the repo's most-read public text — this command encodes the review and hygiene checks that keep them accurate and safe to publish.
Instructions
1. Decide whether to curate at all
Not every release deserves curated notes. Routine patch releases should keep the generated changelog — skipping is a normal outcome, not a failure. Curate when the release is a milestone: a minor, a headline capability, or a version the documentation will reference. If the user invoked this command for a plain patch, say so and confirm they still want curated notes.
2. Establish the version and the range
- The target version comes from the argument (e.g.
/release-notes 1.7.0). If none was given, ask what version the user intends to tag — the filename must match the eventual tag exactly, and a mismatched file is silently ignored. Derive it from the currentpyproject.tomlversion plus the bump type the user will dispatch (1.6.30+minor→1.7.0). - Never bump the version yourself.
create-release.ymlbumpspyproject.tomlonmainas its first step and derives the tag from the result — a hand-bump collides with it. - The range depends on the release kind. A minor memorializes the whole series since the previous minor (
vX.(Y-1).0..origin/main) — patches got generated changelogs; the minor is the digest nobody gets from reading thirty of them. A curated patch or hotfix covers only the span since the last tag:
LAST=$(git tag --sort=-creatordate | head -1) # patch: last tag
# minor: previous minor tag, e.g. v1.6.0 when cutting v1.7.0
git log "$RANGE_START"..origin/main --merges --format='%s'
gh pr list --state merged --limit 30 --json number,title,mergedAt
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.
- 2d ago First seen · 64 lines · 9 tokens per session scan A b5e30b34b42c
release-notes is a command published in the GitHub repository RoboFinSystems/robosystems (24 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9 tokens to every session and 1,303 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
pre-release
Run the pre-release checklist for this project.
make-pr
Your task is to create a PR for the current branch.
wh:bump
Use when bumping Wheeler version after shipping features. Trigger when user says 'bump version', 'release', 'cut a release', 'version bump', 'update version', or after a set of features have been committed and the user wants to formalize a new version.
fill-event-triage
체결(fill) 이벤트, 특히 매도 체결 후 현금 재배치 판단을 read-only 트리아지로 자동 기동해 dry-run 제안을 남긴다. ROB-755.
testflight
Build iOS release IPA and upload a new TestFlight build (auto-bumps CFBundleVersion).
crypto-alert-triage
Command "crypto-alert-triage" from mgh3326/auto_trader, covering crypto-alert-triage, 입력, 1. 맥락 복원 (반드시 이 순서), 2. 분석 and 3. dryrun 미리보기 (read-only).