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/joncik91/ucai/releasegit clone --depth 1 https://github.com/Joncik91/ucaiWhat 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.00011 | $0.01435 |
| Opus 5 | $0.00005 | $0.00718 |
| Sonnet 5 | $0.00002 | $0.00287 |
| Haiku 4.5 | $0.00001 | $0.00144 |
Grade A, and why
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
You are helping a developer prepare a release. This command reads git history since the last tag, generates a changelog, bumps the version, and creates a git tag — all with approval gates.
Core Principles
- Git history is the source of truth: Changelog comes from commits, not guesswork
- Cross-reference specs: Connect releases to planned work via requirements.md
- Never push without permission: Create the tag locally, let the user push
- Approval at every step: Changelog, version bump, and tag each need sign-off
- Track progress: Write and update
tasks/todo.mdto track phase completion
Skill Loading — MANDATORY
Before starting, load the DevOps skill.
- Load
Skill(ucai:devops)— releasing is DevOps work
State that you loaded the skill before proceeding.
Phase 1: Analyze
Goal: Understand the current state and determine the release version.
Input: $ARGUMENTS
Actions:
- Create todo list with all phases (1–4)
- Find current version — check in order, use the first found:
package.json→"version"fieldCargo.toml→versionunder[package]pyproject.toml→versionfieldversion.txt- Git tags:
git describe --tags --abbrev=0 - If no version found anywhere, start at
v0.0.0
- Find last tag:
git describe --tags --abbrev=0 2>/dev/null - Get commits since last tag:
git log <last-tag>..HEAD --oneline- If no tags exist, use
git log --oneline
- If no tags exist, use
- Load project context (if available):
- Check
.claude/requirements.md— identify requirements completed since last release (marked[x])
- Check
- Determine version bump:
- If
$ARGUMENTSspecifies a version (e.g.,v2.1.0): use it directly - If
$ARGUMENTSspecifies a bump type (major,minor,patch): apply to current version - If
$ARGUMENTSis empty: analyze commits and suggest:- Breaking changes (commit messages with "breaking", "BREAKING CHANGE", major refactors) → suggest
major - New features ("add", "feat", "implement", "new") → suggest
minor - Bug fixes and maintenance only → suggest
patch
- Breaking changes (commit messages with "breaking", "BREAKING CHANGE", major refactors) → suggest
- Arbitration when commit messages are ambiguous: If no messages explicitly mention breaking changes but the diff shows renamed exports, removed public API methods, changed function signatures, or removed config options — treat as potentially breaking. Present both options: "Commits suggest minor, but I noticed [specific change] which could be breaking. Recommend minor or major?"
- If
- Present summary to user:
- Current version
- Commits since last release (count + key highlights)
- Completed requirements (if requirements.md exists)
- Proposed new version
- Wait for user to confirm or adjust the version
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 · 149 lines · 11 tokens per session scan A a867fa2efccf
release is a command published in the GitHub repository Joncik91/ucai (29 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 1,435 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
release
Cut a Uni-CLI release from a clean main.
bump
Perform a full version bump: sync main, write changelog, refresh top-level docs, bump version, and push.
ship-ticket
Ship an ALREADY-BUILT ticket — code review → PR → merge → learnings → install-local. Skips the build (you built it in SpecKit Companion). The tail of /fix-tickets, no rebuild.
release-checklist
Tu es un Release Manager expert. Tu dois guider l'équipe à travers toutes les étapes d'une release de qualité, en vérifiant chaque point critique.
release
Prepare a release by updating docs and bumping the version.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.