agentmods.dev

release

A release command for preparing, publishing, and monitoring a new software version. It checks tests, linting, builds, security, dependencies, documentation, version numbers, changelogs, CI/CD runs, and package publication.

In plain words
What is it for?
Use it to choose a version bump, update package files and changelogs, create release commits or tags, monitor automation, and verify that the package was published.
Why use it?
It helps reduce the chance of publishing a broken, undocumented, incorrectly versioned, or unavailable release.

Command for Claude Code

12 7d ago A scan 9 tokens original MIT
View the source file SylphxAI/coderag
Install

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.

agentmods
npx agentmods add commands/sylphxai/coderag/release
Clone the repo
git clone --depth 1 https://github.com/SylphxAI/coderag

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.00547
Opus 5 $0.00005 $0.00273
Sonnet 5 $0.00002 $0.00109
Haiku 4.5 $0.00001 $0.00055

Measured 2d ago against content hash 7c90b2fa5bfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/commands/release.md · 105 lines

What it actually says

Release & Publish

Prepare, publish, and monitor package release.

Pre-Release Checks

Quality Gates:

  • All tests pass
  • No lint errors
  • Build successful
  • No security vulnerabilities
  • Dependencies up to date
  • CHANGELOG updated
  • README accurate
  • Breaking changes documented

Version Decision:

  • Breaking changes → major
  • New features → minor (default)
  • Bug fixes → patch

Release Process

For TypeScript/JavaScript Projects

  1. Create Changeset:

    bunx changeset
    • Select package
    • Choose version bump type
    • Write clear summary

  2. Version Bump:

    bunx changeset version
    • Updates package.json
    • Updates CHANGELOG.md
    • Consumes changeset

  3. Commit & Push:

    git add -A
git commit -m "chore(release): <package>@<version>"
git push

  4. Monitor CI:

    gh run list --workflow=release --limit 5
gh run watch <run-id>

  5. Verify Publication:

    npm view <package>@<version>

For Other Projects

  1. Update version in manifest (package.json, setup.py, etc.)
  2. Update CHANGELOG
  3. Create git tag
  4. Push tag to trigger release
  5. Monitor CI/CD

Post-Release

  • Verify package published
  • Test installation: npm install <package>@latest
  • Create GitHub release with notes
  • Announce (if public package)
  • Close related issues/PRs

Troubleshooting

CI fails on install:

  • Update lockfile locally: bun install
  • Commit and push

Tests fail in CI:

  • Run tests locally: npm test
  • Fix issues, commit, push

Build fails:

  • Check build locally: npm run build
  • Fix errors, commit, push

Exit Criteria

  • Package published successfully
  • CI workflow completed
  • GitHub release created
  • Version verified on registry
  • Installation tested

Report: Version number, publish time, registry URL.

Changes

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.

  1. 2d ago First seen · 105 lines · 9 tokens per session scan A 7c90b2fa5bfd

Subscribe to this mod's changes

release is a command published in the GitHub repository SylphxAI/coderag (12 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 547 once invoked, about $0.0000 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-08-30.

Git and workflowRAGSecurityTestingcode-searchembeddingsmcptfidfvector-search
Related

Other commands, from other repositories

rp-build-cli

Build with rp-cli context builder → chat → implement.

gmickel/gno · 10 tokens

rp-investigate-cli

Deep codebase investigation and architecture research with rp-cli commands.

gmickel/gno · 11 tokens

rp-oracle-export-cli

Export context for oracle consultation using rp-cli.

gmickel/gno · 8 tokens

rp-reminder-cli

Continue your current workflow using rp-cli instead of built-in alternatives.

gmickel/gno · 5 tokens

call-graph

Trace callers, callees, or paths using the call graph.

Helweg/open-codebase-index · 12 tokens

index

Index the codebase for semantic search.

Helweg/open-codebase-index · 7 tokens