Vibeyard is an IDE and project workspace for managing multiple AI coding-agent sessions, including parallel runs, split panes, task boards, cost tracking, and session resumption. It is for developers who use Claude Code, Codex CLI, or Gemini CLI and need to organize many agent-driven coding tasks. The catalogue add-ons provide commands, skills, and instructions for working with Vibeyard.
Borrowing it
Nothing to install: this file belongs to elirantutia/vibeyard. 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/elirantutia/vibeyard/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/elirantutia/vibeyardWrote 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/elirantutia/vibeyard/release)<a href="https://agentmods.dev/commands/elirantutia/vibeyard/release"><img src="https://agentmods.dev/badge/commands/elirantutia/vibeyard/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/elirantutia/vibeyard/release"><img src="https://agentmods.dev/badge/commands/elirantutia/vibeyard/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.00410 |
| Opus 5.5 | $0.00000 | $0.00164 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
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 1mo 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
Perform a full release: generate release notes, bump version, commit, tag, and push.
Instructions
1. Run tests
- Run
npm testand ensure all tests pass before proceeding. If any test fails, stop and report the failure to the user.
2. Determine the new version
- The argument specifies the version bump type or an explicit version.
- If the argument is
major,minor, orpatch, calculate the new version by bumping the corresponding part of the current version inpackage.json. - If the argument is an explicit version (e.g.,
0.3.0orv0.3.0), use that. Strip any leadingv. - If no argument is provided, default to
patch.
3. Generate release notes
- Run the
/release-notesskill with the new version to generate and prepend the changelog entry toCHANGELOG.md.
4. Bump the version and commit
- Use
npm version <major|minor|patch|explicit-version> --no-git-tag-versionto bumppackage.jsonandpackage-lock.jsonwithout creating a git tag yet. - Stage
package.json,package-lock.json, andCHANGELOG.md. - Commit with the message:
release: v<version>
5. Create the git tag
- Create an annotated tag:
git tag -a v<version> -m "v<version>"
6. Confirm before pushing
- Show the user a summary of what was done:
- Version: old → new
- Changelog entries generated
- Commit hash
- Tag name
- Ask the user to confirm before pushing. If confirmed:
git push origin maingit push origin v<version>
- If denied, inform the user the commit and tag are local and can be undone.
$ARGUMENTS
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.
- 1mo ago First seen · 43 lines · 0 tokens per session scan A 3b2276c42bc3
release is a command published in the GitHub repository elirantutia/vibeyard (1,388 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 410 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
release-flow
Portable gated release flow — deterministic gate + vendor-agnostic independent reviewer, runnable from any harness.
release
Prepare a release (step 1 of 2) — version bump and PR. Cutting the tag is a separate operator-only step.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
memo-resume
Restore context from last checkpoint at session start.
aigon-feature-open
Open a feature worktree in terminal and automatically start the AI agent with /aigon-feature-do.
diff-script
Compare an MDL script against the project's current state.