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/raine/workmux/updategit clone --depth 1 https://github.com/raine/workmuxWhat 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.00007 | $0.00404 |
| Opus 5 | $0.00003 | $0.00202 |
| Sonnet 5 | $0.00001 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
update 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.
- `curl` must be available in PATH (used for downloading) What it actually says
Updates workmux to the latest version by downloading the prebuilt binary from GitHub Releases.
workmux update
What happens
- Checks the latest release version from the GitHub API
- Compares with the currently installed version
- Downloads the correct binary for your OS and architecture
- Verifies the SHA-256 checksum
- Atomically replaces the current binary (with rollback on failure)
If workmux is already up to date, it reports this and exits.
Homebrew installs
If workmux was installed via Homebrew, the command will detect this and instruct you to use brew upgrade instead:
brew upgrade workmux
Supported platforms
The command downloads prebuilt binaries for:
- macOS (Apple Silicon / Intel)
- Linux (x86_64 / ARM64)
Automatic update check
Workmux periodically checks for new versions in the background. When an update is available, a one-line notice is printed to stderr:
Update available: workmux v0.1.124 -> v0.1.125 (run `workmux update`)
The check runs at most once every 24 hours via a detached background process and never slows down your commands. The notice is shown at most once per day and only in interactive terminals.
Disabling
To disable the automatic update check, either:
- Set
auto_update_check: falsein the global config (~/.config/workmux/config.yaml) - Set the environment variable
WORKMUX_NO_UPDATE_CHECK=1
Requirements
curlmust be available in PATH (used for downloading)tarmust be available in PATH (used for extraction)sha256sumorshasummust be available (used for checksum verification)- Write permission to the directory containing the workmux binary
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 · 60 lines · 7 tokens per session scan A 55f548eeb1a7
update is a command published in the GitHub repository raine/workmux (2,284 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 404 once invoked, about $0.0000 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.