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/binaryhb0916/isparto/release-ispartogit clone --depth 1 https://github.com/BinaryHB0916/iSpartoWrote 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/binaryhb0916/isparto/release-isparto)<a href="https://agentmods.dev/commands/binaryhb0916/isparto/release-isparto"><img src="https://agentmods.dev/badge/commands/binaryhb0916/isparto/release-isparto.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.00000 | $0.00613 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
release-isparto 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Team Lead. The user has run /release-isparto to publish a new version.
IMPORTANT: Detect the user's language and respond in that same language (Chinese or English only).
Your responsibility: Execute the release process fully automatically. No confirmations, no pauses.
Version calculation
Parse the user's argument (if any) to determine bump type:
/release-ispartoor/release-isparto patch→ patch (X.Y.Z+1)/release-isparto minor→ minor (X.Y+1.0)/release-isparto major→ major (X+1.0.0)
Read the VERSION file, compute the new version number.
Execution
-
Verify preconditions (all must pass — if any fails, follow the recovery path):
- Current branch must be
main— if not, rungit checkout main && git pull - Working tree must be clean — if not, report dirty files and stop
- CHANGELOG.md must have an
[Unreleased]section with content — if empty, execute the changelog prep flow: a.git checkout -b docs/changelog-MMDDb. Write changelog entries under[Unreleased](reviewgit logsince last release tag for changes) c.git add CHANGELOG.md && git commit && git pushd. Create PR viagh pr create, merge viagh pr merge --mergee.git checkout main && git pull && git branch -d docs/changelog-MMDDf. Re-run precondition checks from the top - Tag
v<new-version>must not already exist — if it does, report and stop
- Current branch must be
-
Execute release script:
- Run:
bash scripts/release.sh <new-version> - Monitor output for errors. If any step fails, report the error and the script's suggested recovery command to the user
- Run:
-
Post-release verification:
- Confirm GitHub Release exists:
gh release view v<new-version> - Confirm tag exists locally:
git fetch --tags && git tag -l v<new-version> - Inform the user (in user's language) that v has been published, and include the GitHub Release URL
https://github.com/BinaryHB0916/iSparto/releases/tag/v<new-version>
- Confirm GitHub Release exists:
CRITICAL RULES:
- NEVER run
git tagorgit push origin <tag>directly — the release script handles tagging via GitHub API - NEVER commit directly on main — the release script creates a
release/branch automatically - If the release script fails mid-way, do NOT retry manually — report the error and the recovery command to the user
- This is NOT a development task — do NOT create a feature branch, do NOT spawn Codex, do NOT run Doc Engineer audit. The release script is self-contained.
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 · 44 lines · 0 tokens per session scan A 29284eb6775f
release-isparto is a command published in the GitHub repository BinaryHB0916/iSparto (59 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 613 tokens. 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
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
OPSX: Archive
Archive a completed change in the experimental workflow.
Cairn Vibe Session
Director-driven cairn session that ships a themed release block approved up front, unlike the autonomous one-unit /cairn-loop.
OPSX: Archive
Archive a completed change in the experimental workflow.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
OPSX: Archive
Archive a completed change in the experimental workflow.