domux: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from pranav7/domux. It costs 0 tokens per session (891 once invoked), scanned C, original, Apache-2.0.

A command for releasing the domux project by checking a version, validating the repository, and starting its GitHub release workflow.

In plain words
What is it for?
Preparing a versioned domux release, running the required repository checks, tagging the current commit, pushing the tag, and monitoring the GitHub Action.
Why use it?
It adds checks before creating and pushing a release tag, helping catch invalid versions, unsynced code, failed builds, and failed tests.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is pranav7/domux's own configuration. It tells Claude Code how to work on domux itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything domux configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is sh tests/license/run.sh && sh tests/release/run.sh && sh tests/install/run.sh.

Reuse

Borrowing it

Nothing to install: this file belongs to pranav7/domux. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pranav7/domux/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/pranav7/domux

Made for: Claude Code.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/pranav7/domux/release/github.svg)](https://agentmods.dev/commands/pranav7/domux/release)
Your own site
<a href="https://agentmods.dev/commands/pranav7/domux/release"><img src="https://agentmods.dev/badge/commands/pranav7/domux/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/pranav7/domux/release"><img src="https://agentmods.dev/badge/commands/pranav7/domux/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 891 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00891
Opus 5.5 $0.00000 $0.00356
Sonnet 5.5 $0.00000 $0.00178
Haiku 4.5 $0.00000 $0.00089

Measured 1mo ago against content hash 50ac5282fece, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

release scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

sh -c 'curl -fsSL https://domux.dev/install.sh | sh'

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

sh -c 'curl -fsSL https://domux.dev/install.sh | sh'
.claude/commands/release.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release domux $ARGUMENTS (a version such as 0.1.2; ask for one if it is missing).

Work through these in order and stop at the first thing that does not hold. Every failure names what to do next; do that rather than working around it.

1. The version is a real next version

  • git status --short is empty and the branch is the one releases come from.
  • git fetch origin --prune --prune-tags --force makes the tags here the tags on GitHub, so a tag deleted there is not taken for the newest one.
  • The version is greater than the newest tag: git tag --sort=-v:refname | head -3.
  • The version is the next patch, such as 0.1.2 after 0.1.1, unless the author asks for another. The number stays low while domux is young, and the changelog carries what changed.

2. The tree is green

cargo fmt --all --check
cargo build --workspace --locked
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --locked -- --test-threads=4
sh tests/license/run.sh && sh tests/release/run.sh && sh tests/install/run.sh

3. The release commit

  • Set version under [workspace.package] in Cargo.toml to the new version, then cargo build --workspace --locked so Cargo.lock follows.
  • Write the CHANGELOG.md section: ## [<version>] - <today> with ### Added, ### Changed, ### Fixed or ### Removed under it, and the compare link at the bottom of the file. Read git log --oneline <last tag>..HEAD and write what a reader of the release notes needs, not a list of commits.
  • Open the section with one line and a blank line after it: what the release brings, as a short list separated by commas, in 50 characters or fewer, with no markdown and no full stop, such as Themes, a leader you pick, Linux fixes. domux.dev shows that line beside the newest version.
  • sh scripts/release/check-version.sh v<version> and sh scripts/release/changelog-section.sh <version> both answer.
  • Commit: Release <version>.

4. Ask the author

Print the version, the changelog section and the commit, and ask before the tag. A tag that is pushed is public; nothing after this point is undone quietly.

Read the full file on GitHub · 82 lines

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. 1mo ago Changed · +6 lines 50ac5282fece
  2. 1mo ago Changed · +4 lines 823332035a5d
  3. 1mo ago Changed · +16 lines · -16 tokens per session scan A → C 5a7c2415403e
  4. 1mo ago First seen · 56 lines · 16 tokens per session scan A a5292f1c5352

Subscribe to this mod's changes

release is a command published in the GitHub repository pranav7/domux (8 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 891 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.