path

A command that prints the filesystem location of an existing Git worktree. A worktree is a separate working directory for a branch in the same repository.

In plain words
What is it for?
Use it to change into a worktree directory, copy files there, or pass its path to other commands.
Why use it?
It avoids manually finding the directory when you need to navigate to it or use it in a script.

Command

Install

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.

agentmods
npx agentmods add commands/raine/workmux/path
Clone the repo
git clone --depth 1 https://github.com/raine/workmux
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00142
Opus 5 $0.00004 $0.00071
Sonnet 5 $0.00002 $0.00028
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash e219d5385ea6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

path 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 yesterday.

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.

docs/src/content/docs/reference/commands/path.md · 29 lines

What it actually says

Prints the filesystem path of an existing worktree. Useful for scripting or quickly navigating to a worktree directory.

workmux path <name>

Arguments

  • <name>: Worktree name (the directory name).

Examples

# Get the path of a worktree
workmux path user-auth
# Output: /Users/you/project__worktrees/user-auth

# Use in scripts or with cd
cd "$(workmux path user-auth)"

# Copy a file to a worktree
cp config.json "$(workmux path feature-branch)/"
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. yesterday First seen · 29 lines · 8 tokens per session scan A e219d5385ea6

Subscribe to this mod's changes

path is a command published in the GitHub repository raine/workmux (2,284 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 142 once invoked, about $0.0000 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.