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 skills/greglas75/zuvo/release-docsnpx skills add greglas75/zuvo --skill release-docsgit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/skills/greglas75/zuvo/release-docs)<a href="https://agentmods.dev/skills/greglas75/zuvo/release-docs"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/release-docs.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.00044 | $0.02626 |
| Opus 5 | $0.00022 | $0.01313 |
| Sonnet 5 | $0.00009 | $0.00525 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade A, and why
release-docs 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 yesterday.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:release-docs
Sync documentation with a release. Only updates docs whose source files actually changed.
Mandatory File Loading
Read these files before proceeding:
CORE FILES LOADED:
1. ../../shared/includes/env-compat.md — READ
2. ../../shared/includes/run-logger.md — READ
3. ../../shared/includes/retrospective.md — READ
Argument Parsing
| Input | Effect |
|---|---|
| (no flags) | Auto-detect range from memory/last-ship.json or git tags |
<range> |
Explicit git range (e.g., v1.1.0..v1.2.0) |
--dry-run |
Show proposed changes without writing |
Dispatch is already authorized — do not ask, do not downgrade. Invoking this skill IS the
request for every agent and gate it mandates, so a session rule about unprompted Agent use does not
apply here. Only a harness with NO dispatch capability takes the documented single-agent fallback,
and it still runs every gate inline — see ../../shared/includes/env-compat.md. Skipping a mandated
agent and self-scoring the result is a substituted gate, not a degraded run.
Phase 0: Determine Range and Suffix
- If an explicit
<range>argument was provided: use it. Skip remaining steps in this phase. - Else if
memory/last-ship.jsonexists: read therangefield (SHA-based, e.g.,"abc1234..def5678") and use it directly forgit diff. Also readpreviousTagandnewTagfor display in the output block. If the artifact uses a legacy version-based range (e.g.,"v1.1.0..v1.2.0"), fall back to it but log: "Warning: legacy version-based range — consider re-running zuvo:ship for SHA-based artifact." - Else: derive from git tags.
- Run
git describe --tags --abbrev=0to get the latest tag. - Run
git describe --tags --abbrev=0 <latest-tag>^to get the previous tag. - Construct range as
<previous-tag>..<latest-tag>.
- Run
- If no range can be derived after the above steps:
- Interactive environments: ask the user to provide a range explicitly.
- Non-interactive environments (Codex App, Cursor): print
[AUTO-DECISION]: no range derivable. Skipping documentation sync.and exit with PASS verdict.
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.
- yesterday First seen · 203 lines · 44 tokens per session scan A f9d8146becb4
release-docs is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 2,626 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
ship
/ship - Release Pipeline Commander.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
changelog
Render release notes / a changelog from the cladding spec. Use when the user asks for release notes, a changelog, 릴리즈 노트, 변경 이력, or "what changed (since )" — run clad changelog --json for the deterministic shipped-changes manifest, then write the human-facing notes FROM it, sourcing every claim from a feature title or…