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/paulpreibisch/agentvibes/releasegit clone --depth 1 https://github.com/paulpreibisch/AgentVibesWrote 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/paulpreibisch/agentvibes/release)<a href="https://agentmods.dev/commands/paulpreibisch/agentvibes/release"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/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.1 | $0.00016 | $0.03130 |
| Opus 5 | $0.00008 | $0.01565 |
| Sonnet 5 | $0.00003 | $0.00626 |
| Haiku 4.5 | $0.00002 | $0.00313 |
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 3d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Semi-automated release process with AI-generated release notes and human approval checkpoints.
This command:
- Runs full test suite - MUST pass before proceeding ✅
- Validates Sonar quality gates - MUST pass before proceeding ✅
- Analyzes all changes since the last release (git log + diffs)
- Reads actual code changes to understand context
- Generates AI summary and release notes
- PAUSES for human review of RELEASE_NOTES.md ⏸️
- PAUSES for human review of AI summary ⏸️
- Updates installer.js and update scripts with AI summary
- Updates README.md with new version and release info ⚠️
- Bumps the version using npm version
- Commits everything together (including updated README)
- Pushes to master with --follow-tags
- Creates GitHub release
- Publishes to npm (packages README at this moment!)
⚠️ CRITICAL ORDER: README must be updated (step 8) BEFORE npm publish (step 13) because npm packages whatever README exists at publish time. This ensures the npm package page displays current release info.
🧪 TEST REQUIREMENT: The test suite MUST pass before any release operations begin. If tests fail, the release is aborted immediately. This prevents publishing broken code to npm.
🛡️ SONAR QUALITY GATES: All SonarCloud quality requirements from CLAUDE.md MUST be validated before release:
Shell Script Security (Bash)
- ✅ All bash scripts MUST have
set -euo pipefailat the top (strict mode) - ✅ All variables MUST be quoted (e.g.,
"$VARIABLE", not$VARIABLE) - ✅ No hardcoded credentials (API keys, passwords, tokens)
- ✅ Input validation for all external inputs
- ✅ Secure temp directories (
$XDG_RUNTIME_DIRwith fallback) - ✅ Path traversal prevention
- ✅ File ownership verification before processing
- ✅ Single quotes in trap statements (deferred expansion)
JavaScript/Node.js Security
- ✅ Use
path.resolve()for path operations - ✅ Path safety validation (prevent traversal)
- ✅ No sensitive data in logs (mask credentials)
- ✅ Try-finally for resource cleanup
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.
- 3d ago First seen · 342 lines · 16 tokens per session scan A 1b29dc1c72c8
release is a command published in the GitHub repository paulpreibisch/AgentVibes (153 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 3,130 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-09-03.
Other commands, from other repositories
rollback
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
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.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).