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/osiris-devworks/smart-citizen/start_releasegit clone --depth 1 https://github.com/Osiris-DevWorks/smart-citizenWhat 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.00022 | $0.01128 |
| Opus 5 | $0.00011 | $0.00564 |
| Sonnet 5 | $0.00004 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
start_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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/start_release
Open the next integration branch per the documented release model. Bumps VERSION.TXT and commits the kickoff change locally. Does not push — the user pushes when ready.
Argument
$ARGUMENTS — required, one of major, minor, patch. Determines how to bump the current VERSION.TXT:
major:X.Y.Z→(X+1).0.0minor:X.Y.Z→X.(Y+1).0patch:X.Y.Z→X.Y.(Z+1)
If $ARGUMENTS is empty or not exactly one of the three values, abort and ask the user for the missing arg. Do not guess.
Procedure
Stop on the first failure of any step. Never proceed past a failed check.
1. Validate the argument
$ARGUMENTS must be exactly major, minor, or patch (case-sensitive). Otherwise abort with: "/start_release requires one of: major, minor, patch".
2. Read and parse VERSION.TXT
Read VERSION.TXT. Strip whitespace. Split on . — must yield exactly three non-negative integers. If parsing fails, abort with the offending content.
3. Compute the next version
major→ bump first part, reset second and third to0minor→ bump second part, reset third to0patch→ bump third part only
Build NEW_VERSION = "X.Y.Z" and NEW_BRANCH = "release/X.Y.Z".
4. Safety preconditions
Run each. Abort on the first failure.
- On main:
git branch --show-currentmust equalmain. If not, abort: "Switch to main before starting a release." - Clean working tree:
git status --porcelainmust be empty. If dirty, abort and list the offending files: "Working tree has uncommitted changes; commit or stash before starting a release." - main up to date with origin (best-effort): try
git fetch origin main. If the fetch succeeds, checkgit rev-list --count main..origin/main. If > 0, abort: "Local main is behind origin/main. Pull before starting a release." If the fetch itself fails (no network, no origin), warn the user but proceed — don't block on offline work. - Branch does not already exist:
- Local:
git rev-parse --verify NEW_BRANCHmust fail (exit non-zero). If it succeeds, abort: "NEW_BRANCH already exists locally." - Remote:
git ls-remote --heads origin NEW_BRANCHmust return empty. If non-empty, abort: "NEW_BRANCH already exists on origin."
- Local:
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 · 86 lines · 22 tokens per session scan A 82f7d8136f61
start_release is a command published in the GitHub repository Osiris-DevWorks/smart-citizen (99 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,128 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
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
release
You are a release agent for the Rivet project. Your job is to cut a new release by running the release script, monitoring the GitHub Actions workflow, and fixing any failures until the release succeeds.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Command "release" from Besty0728/Unity-Skills, covering release workflow — 候选矩阵 → main/tag → 正式 release, 输入, 阶段 1：只读预检查, 阶段 2：生成并审阅 release note and v{version} — {一句话总结，提炼 2-4 个核心特性}.
android-release
Prepare and execute an Android release (patch/minor/major).