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/binsarjr/termul/release-terminalgit clone --depth 1 https://github.com/binsarjr/termulWrote 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/binsarjr/termul/release-terminal)<a href="https://agentmods.dev/commands/binsarjr/termul/release-terminal"><img src="https://agentmods.dev/badge/commands/binsarjr/termul/release-terminal.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.1 | $0.00025 | $0.01344 |
| Opus 5 | $0.00013 | $0.00672 |
| Sonnet 5 | $0.00005 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
release-terminal scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(git:*), Bash(gh:*), Bash(curl:*), Bash(python3:*), Read, Edit, Write How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are cutting a new release of Termul (binsarjr/termul). Work through the steps in order. If any step fails, stop and report — never continue past a failure, and never publish a broken build.
Key fact that drives everything: Tauri reads the released version from src-tauri/tauri.conf.json (version), not from the git tag. So the version file must be bumped and committed before tagging, and the tag must point at that bump commit.
0. Preflight
gh auth statusmust be authed; abort if not.git fetch origin main --tags.- Last tag:
git describe --tags --abbrev=0 origin/main(e.g.v0.1.0). If there are no tags, treat the previous version as0.0.0. - Commits since:
git log <lasttag>..origin/main --oneline. If empty → stop: "Nothing to release; no commits since ."
1. Decide the new version ← the one confirmation gate
- Current version = last tag without the
v. - If
$ARGUMENTSis given:patch/minor/major→ apply that bump; an explicitX.Y.Z→ use it verbatim. - Otherwise auto-detect from the conventional commits since the last tag:
feat!:/fix!:/ aBREAKING CHANGE:footer → major- else any
feat:→ minor - else (
fix:,chore:,refactor:, …) → patch
- Compute the new version and tag
vX.Y.Z. - Show the user: the commit list, the detected bump type, and
current → new. Wait for an explicit "yes" before continuing. This is the only interactive gate.
2–3. Bump + commit + tag (in a throwaway worktree, so other working trees are untouched)
Run all git mutations through a temporary worktree off the freshly-fetched origin/main — never touch the user's main checkout (another agent may be working there):
git worktree add /tmp/termul-release origin/main --detach
In /tmp/termul-release:
- Edit
src-tauri/tauri.conf.json→ set"version"to the new version. - Edit
package.json→ set"version"to the new version. - Do not touch
src-tauri/Cargo.tomlorCargo.lock—tauri.conf.jsonis the source of truth for the released version, and leavingCargo.*unchanged keeps the--lockedCI green. - Commit and push the bump to main, then tag that commit and push the tag:
git -C /tmp/termul-release commit -am "chore(release): vX.Y.Z"
git -C /tmp/termul-release push origin HEAD:main
git -C /tmp/termul-release tag vX.Y.Z
git -C /tmp/termul-release push origin vX.Y.Z # ← triggers the Release workflow
git worktree remove /tmp/termul-release --force
(Substitute the real version. The tag now points at the bump commit, so the build produces correctly-versioned artifacts.)
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.
- 5d ago First seen · 78 lines · 25 tokens per session scan A c9787bdefef2
release-terminal is a command published in the GitHub repository binsarjr/termul (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,344 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
canaryrelease
Trigger a canary build of the desktop app (rolling internal-testing release, not a versioned stable release).
release
Use Github CLI to change the latest version draft release to a published release on the repo djyde/ccmate-release.
publish
Use GitHub CLI to trigger the "publish" workflow with inputs.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.