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/renamegit 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.00015 | $0.00502 |
| Opus 5 | $0.00008 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
rename 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renames a worktree's directory, its tmux window or session, and the per-worktree workmux metadata stored in git config. Optionally also renames the underlying git branch.
workmux rename [old-name] <new-name> [--branch]
Arguments
[old-name]: Optional current worktree name (the directory name). Defaults to the current worktree when run from inside one.<new-name>: The new handle. This becomes the worktree directory name and the tmux window/session base name.
Options
| Flag | Description |
|---|---|
--branch, -b |
Also rename the underlying git branch to match <new-name>. Fails if the worktree is on a detached HEAD. |
What gets renamed
- The worktree directory (
git worktree move) - The tmux window or session (matching duplicates like
wm-feature-2are renamed preserving their-Nsuffix) workmux.worktree.<handle>.*git config entries (e.g. the stored window/session mode)- Agent state files in
$XDG_STATE_HOME/workmux/agents/*.json(updatesworkdir,window_name,session_name) - Sandbox container marker directory, if present
- The local git branch, only when
--branchis passed
Examples
# Rename a worktree from inside it
workmux rename feature-new
# Rename a specific worktree by name
workmux rename feature-old feature-new
# Also rename the branch to match
workmux rename feature-old feature-new --branch
Notes
- The main worktree cannot be renamed.
- Rename is non-destructive: uncommitted changes and untracked files survive.
- Submodules are not handled specially;
git worktree movewill error out if the worktree contains submodules. - Any shell already running inside the old directory will have a stale
$PWDafter the rename. Runcd(orcd <new-path>) to refresh. - Collisions are rejected up front: if the new path, tmux target, or branch already exists, the command aborts before making any 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.
- 3d ago First seen · 54 lines · 15 tokens per session scan A da244974f5c3
rename is a command published in the GitHub repository raine/workmux (2,351 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 502 once invoked, about $0.0001 per session on Opus 5. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.