Borrowing it
Nothing to install: this file belongs to sijeeshmiziha/visionagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sijeeshmiziha/visionagent/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/sijeeshmiziha/visionagentWrote 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/sijeeshmiziha/visionagent/release)<a href="https://agentmods.dev/commands/sijeeshmiziha/visionagent/release"><img src="https://agentmods.dev/badge/commands/sijeeshmiziha/visionagent/release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sijeeshmiziha/visionagent/release"><img src="https://agentmods.dev/badge/commands/sijeeshmiziha/visionagent/release.svg" alt="Reviewed on agentmods" width="80" 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.00401 |
| Opus 5.5 | $0.00000 | $0.00160 |
| Sonnet 5.5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 2mo 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
Release Workflow
Prepare and publish a new release of VisionAgent to npm.
Arguments
$ARGUMENTS (Provide: patch | minor | major — defaults to patch if not specified)
Pre-flight Checks
Run all quality gates first and DO NOT proceed if any fail:
npm run ci
If npm run ci fails, stop and report the failures. Do not release broken code.
Release Steps
1. Determine version type
patch— bug fixes, no API changes (e.g., 0.0.1 → 0.0.2)minor— new features, backwards-compatible (e.g., 0.1.0 → 0.2.0)major— breaking changes (e.g., 0.0.x → 1.0.0)
2. Check CHANGELOG.md
- Read the current CHANGELOG.md
- Verify there are entries for the changes being released
- If CHANGELOG.md is not updated, update it now with the changes from recent commits
3. Check README.md
- Verify any new public API is documented
- If new tools/agents/features were added, ensure they appear in README.md
4. Run the release command
# Based on the version type:
npm run release:patch
# or
npm run release:minor
# or
npm run release:major
This command: bumps the version in package.json, creates a git tag, and pushes to origin. The GitHub Actions release workflow will automatically build and publish to npm.
5. Verify
After the tag is pushed:
- Check GitHub Actions: the release workflow should trigger
- Monitor the workflow run for success
- Verify the new version appears on npm after the workflow completes
Report the new version number and the GitHub Actions URL for the release workflow.
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.
- 2mo ago First seen · 62 lines · 0 tokens per session scan A b1af7257b182
release is a command published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 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-31.
Other commands, from other repositories
generate-changelog
Génération Automatique du Changelog.
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
release-checklist
Obsolète (retirée en 9.0) : utilisez /gate:check release.
forge-update
A command for updating the Claude Forge framework from its remote Git repository. It can check for updates, pull them, and run post-update steps.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.