Borrowing it
Nothing to install: this file belongs to easyhooon/dari. 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/easyhooon/dari/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/easyhooon/dariWrote 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/easyhooon/dari/release)<a href="https://agentmods.dev/commands/easyhooon/dari/release"><img src="https://agentmods.dev/badge/commands/easyhooon/dari/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/easyhooon/dari/release"><img src="https://agentmods.dev/badge/commands/easyhooon/dari/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.01443 |
| Opus 5.5 | $0.00000 | $0.00577 |
| Sonnet 5.5 | $0.00000 | $0.00289 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade A, and why
release scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -sI https://repo1.maven.org/maven2/io/github/easyhooon/dari-gradle-plugin/<version>/dari-gradle-plugin-<version>.pom` How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are releasing a new version of dari. Arguments: $ARGUMENTS
<version>(e.g.2.3.0): a full release. The library and the Gradle plugin go to Maven Central and the desktop app ships with the same number.desktop <version>(e.g.desktop 2.2.2): a desktop-only release. Nothing goes to Maven Central.- No version: read it from
gradle/libs.versions.toml, usingdarifor a full release anddariDesktopfordesktop.
Both releases share one number line, set in gradle/libs.versions.toml: dari is the library, dariDesktop is the desktop app. They differ only after a desktop-only release.
The desktop updater, install-desktop.sh and the download page all read GitHub's /releases/latest, so every GitHub release needs the desktop installers, a plain semver tag, and must not be a draft or prerelease. Apps keep working on any library version from 2.0.0 because compatibility is decided by InspectorProtocol.VERSION, not by these numbers.
Step 1: Pick the mode and verify the version
- Everything going into the release must already be merged to
mainwith CI green. If a feature PR is still open, verify it (and wait for its checks) and merge it first. - Run
gh release list --limit 3and note the latest tag. The new version must be higher, or installed desktop apps never see it. - Full release: set both
darianddariDesktopto the version. - Desktop-only release: set only
dariDesktop; leavedarialone.- First run
git diff --stat <latest_tag>..HEAD -- dari dari-core dari-noop dari-runtime dari-inspector-protocol dari-gradle-plugin. If it lists anything, stop and ask the user: library or protocol changes need a full release, or apps never get them.
- First run
- Make the bump in a PR: branch
chore/bump-desktop-<version>(orchore/bump-version-<version>for a full release) fromorigin/main, commitchore: bump the desktop app to <version>, open the PR, wait for CI, then merge it. - The bump must be on
mainbefore tagging, becausedesktop-release.ymlchecks out the tag and fails whendariDesktopdoesn't match it.
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 · 60 lines · 0 tokens per session scan A dbd6688a4779
release is a command published in the GitHub repository easyhooon/dari (38 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,443 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.
Other commands, from other repositories
msd-release
Run the full mobile app release pipeline for iOS and/or Android.
msd-checklist
Walk through the First Release checklist for App Store or Play Store step by step — AI marks automated steps done, prompts you for manual steps.
msd-bump
Bump the app version number for iOS and Android.
msd-validate
Run all pre-release validation checks without submitting.
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.