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/christopherlouet/claude-base/ops-releasegit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/ops-release)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-release"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-release.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.00000 | $0.00302 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
ops-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 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.
What it actually says
RELEASE Agent
Release workflow with changelog and versioning.
Request context
$ARGUMENTS
Objective
Guide the full release process: version bump, changelog, release branch, tag, merge and GitHub Release.
Workflow
- Check the project state (tests pass, build OK, dependencies up to date)
- Determine the version according to SemVer (MAJOR, MINOR, PATCH)
- Generate the changelog (Added, Changed, Fixed, Deprecated, Removed, Security)
- Create the release branch and bump the version
- Merge into main, create the tag, push
- Merge into develop, create the GitHub Release
- Post-release: check the deployment, announce, document
Expected output
- Version determined with justification
- Changelog in Keep a Changelog format
- Commands executed (branch, tag, merge, push)
- Checklist pre and post-release
Related agents
| Agent | Usage |
|---|---|
/doc:doc-changelog |
Generate the changelog |
/ops:ops-ci |
Automate the release |
/qa:qa-security |
Audit before release |
/ops:ops-monitoring |
Check post-release |
IMPORTANT: Test the release in staging before production.
IMPORTANT: Always have a rollback plan.
YOU MUST update the changelog.
NEVER release on a Friday evening (except for emergencies).
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 · 48 lines · 0 tokens per session scan A 698e76889e22
ops-release is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 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-09-03.
Other commands, from other repositories
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
release
(dev-only) release maintainer harness — MoAI-ADK production release (Enhanced GitHub Flow, scripts/release.sh + GoReleaser). NOT distributed to user projects.
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
launch
Preview the public launch — the file bundle, the secret/PII scan, and the release gates — in dry-run mode, cut a release by deriving its version and composing its changelog, and scaffold the changelog-driven release gate into a managed repo. The preview performs zero writes; ship writes the dated CHANGELOG heading and…
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.