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.
git clone --depth 1 https://github.com/olo-dot-io/Uni-CLIWrote 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/olo-dot-io/uni-cli/release)<a href="https://agentmods.dev/commands/olo-dot-io/uni-cli/release"><img src="https://agentmods.dev/badge/commands/olo-dot-io/uni-cli/release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/olo-dot-io/uni-cli/release"><img src="https://agentmods.dev/badge/commands/olo-dot-io/uni-cli/release.svg" alt="Reviewed on agentmods" width="80" 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.00468 |
| Opus 5.5 | $0.00000 | $0.00187 |
| Sonnet 5.5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
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 1mo 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.
What it actually says
/release — atomic version bump + publish
Cut a Uni-CLI release from a clean main.
Usage
/release <version> [codename]
Example: /release 0.212.0 "Shatalov"
What it does
- Confirms
mainis clean and up to date with origin. - Runs
npm run verify(must pass). - Runs
npm run changeset:versionto fold pending changesets intoCHANGELOG.mdand bumppackage.json. - Updates the six other files that must change atomically (AGENTS.md
counts, README badges/footer,
docs/ROADMAP.mdprogress,docs/TASTE.mdcurrent-version, codename series). Handled byscripts/release.ts. - Runs
npm run verifyagain (regenerated AGENTS.md must be clean). - Creates a single commit:
release: v<version> — <codename>. - Tags
v<version>with annotated message. - Shows what will happen on
git push origin main --tags:- Release workflow triggers, publishes to npm with provenance
via OIDC (see
contributing/release.md). - GitHub release drafted from changelog.
- Release workflow triggers, publishes to npm with provenance
via OIDC (see
Safety
- NEVER push without explicit user confirmation.
- NEVER run
npm publishlocally from this command — CI owns publish. - NEVER skip
verify— a red build becomes a red published package. - NEVER amend or force-push an existing tag.
What you see
Cut release v0.212.0 — Shatalov
package.json 0.211.2 → 0.212.0
CHANGELOG.md +47 lines
AGENTS.md 195 → <new> sites, 956 → <new> commands
README.md badges updated
docs/ROADMAP.md phase 8 marked ✓
docs/TASTE.md current version line
Verify: 881 tests passed, build green.
Next step: git push origin main --tags
(type `y` to push now, `n` to stop here)
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A b16fe2d69f93
release is a command published in the GitHub repository olo-dot-io/Uni-CLI (235 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 468 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
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.
ia-document-release
Post-ship documentation sync. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, and optionally bumps the version.
ia-changelog
Create engaging changelogs for recent merges to main branch.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
versioning
Universal version file discovery and sync. Works with any project structure.
release
Generate changelog, bump version, and create git tag.