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.
npx agentmods add commands/pranav7/domux/releasegit clone --depth 1 https://github.com/pranav7/domuxWhat 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 | $0.00016 | $0.00602 |
| Opus 5 | $0.00008 | $0.00301 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Print the URL and the asset list so the user can verify the curl installer one-liner will resolve correctly. How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a new domux release at version $ARGUMENTS.
The release flow for this repo is:
- Tag pushed to GitHub →
.github/workflows/release.ymlbuilds darwin arm64 + amd64 binaries → publishes a GitHub release with tarballs +SHA256SUMS.
Do the following in order. Stop and report if any step fails — do not retry destructively.
1. Validate the version
$ARGUMENTSmust look likevMAJOR.MINOR.PATCH(e.g.v0.1.0). Reject anything else.- Run
git tag --list "$ARGUMENTS"— if the tag already exists, stop and tell the user.
2. Verify clean release state
git rev-parse --abbrev-ref HEADmust equalmain. If not, stop.git fetch origin mainthen verifygit rev-parse HEAD == git rev-parse origin/main. If local is ahead, ask the user to push first. If behind, ask before fast-forwarding.git status --porcelain— warn the user if the working tree is dirty, but proceed if they confirm (in-progress unrelated work is common here).- Confirm
go build ./...andgo test ./...both pass on the current HEAD. If either fails, stop.
3. Confirm with the user
Show a one-line summary like:
Release v0.2.0 at <short-sha> "<commit subject>" — push tag and trigger CI?
Wait for explicit confirmation before continuing.
4. Tag and push
git tag -a $ARGUMENTS -m "Release $ARGUMENTS"git push origin $ARGUMENTS
5. Watch the workflow
gh run list --workflow=release.yml --limit 1 --json databaseId,status,conclusion,headBranchto find the run.gh run watch <run-id> --exit-statusto follow it. If it fails, print the failed job's log tail and stop — do not retry without user input.
6. Report the release URL
When the workflow succeeds:
gh release view $ARGUMENTS --json url,assets --jq '{url, assets: [.assets[].name]}'- Print the URL and the asset list so the user can verify the curl installer one-liner will resolve correctly.
Notes
- Never use
--forceon the tag push. - If the user passes no version, ask which version they want — don't auto-bump silently.
- This command does NOT merge feature branches. Run that yourself before tagging.
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.
- 2d ago First seen · 56 lines · 16 tokens per session scan A a5292f1c5352
release is a command published in the GitHub repository pranav7/domux (5 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 602 once invoked, about $0.0001 per session on Opus 5. 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-08-31.
Other commands, from other repositories
refresh-compare-pages
Freshly research, add, and refresh marketing compare pages, then open a descriptive PR.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
autospec.plan
Generate YAML implementation plan from feature specification.
issues-exec-plan
複数Issueの並列作業可否を分析し、実行計画をまとめるエピックIssueを作成.
uat
実機受入テスト（UAT）の計画・レビュー・実行・報告を自動化.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.