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/sprklai/zenii/release-taggit clone --depth 1 https://github.com/sprklai/zeniiWrote 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/sprklai/zenii/release-tag)<a href="https://agentmods.dev/commands/sprklai/zenii/release-tag"><img src="https://agentmods.dev/badge/commands/sprklai/zenii/release-tag.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.00000 | $0.02762 |
| Opus 5 | $0.00000 | $0.01381 |
| Sonnet 5 | $0.00000 | $0.00552 |
| Haiku 4.5 | $0.00000 | $0.00276 |
Grade A, and why
release-tag 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 6d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Tag: Version Bump, Commit, Tag & Push
This command orchestrates the full release workflow: version bump across all files, CHANGELOG update, Cargo.lock generation, secret scan, commit, tag, and push to trigger GitHub Actions release builds.
It runs fully automatically with NO user prompts unless secrets are found or --dry-run is specified.
Arguments
$ARGUMENTS
Parse the arguments string for:
- Bump type (REQUIRED):
patch,minor, ormajor - --message "..." (optional): Custom CHANGELOG/release notes. If omitted, auto-generate from commits since last tag.
- --dry-run (optional): Show what would happen without executing any changes.
- --docker (optional): After pushing, trigger a separate Docker image build (~3 hours, multi-arch). Docker does NOT build on normal releases — only when this flag is passed.
If no bump type is provided, STOP and print usage:
Usage: /release-tag <patch|minor|major> [--message "Release notes"] [--dry-run] [--docker]
Examples:
/release-tag patch
/release-tag minor --message "Added channel integrations"
/release-tag major --dry-run
/release-tag patch --docker
Instructions
Follow these steps strictly and sequentially. Stop immediately if any step fails. Do NOT ask the user for confirmation between steps (except for secret detection) — proceed automatically.
Step 1: Verify clean state
Run git status --porcelain to check for uncommitted changes.
If there ARE uncommitted changes, STOP and tell the user:
RELEASE BLOCKED: Uncommitted changes detected.
Please commit or stash your changes before releasing:
git stash # to stash changes
git commit -am "..." # to commit changes
Also run git branch --show-current to confirm we are on the main branch.
If NOT on main, STOP and tell the user: "You are on branch X, not main. Switch to main before releasing."
Step 2: Determine versions
Run the version-bump script in a subshell or read the current version from Cargo.toml to determine:
- Current version: from
grep -m1 '^version = "' Cargo.toml - New version: computed from the bump type
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.
- 6d ago First seen · 263 lines · 0 tokens per session scan A bb2f8834b3af
release-tag is a command published in the GitHub repository sprklai/zenii (23 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,762 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
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.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release
Walk the llmwiki release process step by step.