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/oxygen-fragment/claude-modularWrote 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/oxygen-fragment/claude-modular/prepare-release)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/prepare-release"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/prepare-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.00000 | $0.00633 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
prepare-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 7d 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
Prepare Release Command
2. **Version Management**
- Analyze changes for semantic versioning
- Update version numbers in all relevant files
- Generate version tags and release branches
- Update dependency versions if needed
3. **Changelog Generation**
- Collect commits since last release
- Categorize changes (features, fixes, breaking)
- Generate human-readable changelog
- Create release notes and migration guides
4. **Build and Artifact Creation**
- Execute production build process
- Generate deployment artifacts
- Create container images if applicable
- Sign and verify build artifacts
5. **Documentation Updates**
- Update API documentation
- Refresh user guides and tutorials
- Update installation and setup instructions
- Generate deployment documentation
6. **Release Validation**
- Validate deployment readiness
- Verify rollback procedures
- Check monitoring and alerting setup
- Confirm backup and recovery plans
# Release preparation:
# - Version bump: 1.2.3 → 1.2.4
# - Bug fix changelog
# - Security updates
# - Quick deployment
```
```bash
# Prepare major release
/deploy:prepare-release --type=major
# Major release preparation:
# - Version bump: 1.2.3 → 2.0.0
# - Breaking changes documentation
# - Migration guides
# - Extensive testing
```
```bash
# Prepare release with custom notes
/deploy:prepare-release --notes="Critical security update"
# Custom release preparation:
# - Special release notes
# - Targeted deployment
# - Emergency procedures
# - Stakeholder communication
```
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.
- 7d ago First seen · 98 lines · 0 tokens per session scan A f7c66f1fe0ad
prepare-release is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 633 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
update-changelog
Update CHANGELOG.md with new entry based on git diff.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
release
You are executing the release workflow for a project with a dev → main branch protocol.
deploy
Deploy with pre-flight validation and safety checks.
changelog
You are computing a changelog from the three-document triangle (VISION.md, SPEC.md, BUILDING.md).