gru: Command for Claude Code

.claude/commands/setup-worktree.md

setup-worktree is a command for Claude Code from fotoetienne/gru. It costs 12 tokens per session (367 once invoked), scanned A, original, Apache-2.0.

A command that creates an isolated Git worktree and branch for a GitHub issue.

In plain words
What is it for?
It is for finding the issue and repository, creating the required Gru worktree, and reporting where to continue with gru do.
Why use it?
It gives each issue its own working directory, so changes can be developed without mixing them with other work.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is fotoetienne/gru's own configuration. It tells Claude Code how to work on gru 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 gru configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fotoetienne/gru. 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/fotoetienne/gru/main/.claude/commands/setup-worktree.md
Clone the repo
git clone --depth 1 https://github.com/fotoetienne/gru

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 setup-worktree

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/fotoetienne/gru/setup-worktree"><img src="https://agentmods.dev/badge/commands/fotoetienne/gru/setup-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 367 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00012 $0.00367
Opus 5.5 $0.00005 $0.00147
Sonnet 5.5 $0.00002 $0.00073
Haiku 4.5 $0.00001 $0.00037

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

Security

Grade A, and why

setup-worktree 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 2mo 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.

.claude/commands/setup-worktree.md · 44 lines

What it actually says

Create a git worktree using Gru's filesystem structure for working on an issue.

Issue: $ARGUMENTS

Steps

1. Fetch Issue Details

  • Use gh issue view $ARGUMENTS to get the issue title and number
  • Extract the issue number for naming the branch and worktree

2. Determine Repository Info

  • Get the repository owner and name from git remote
  • Parse from git remote get-url origin

3. Setup Gru Filesystem Structure

  • Ensure bare repo exists at ~/.gru/repos/owner/repo.git/
    • If not, create it: git clone --bare <remote-url> ~/.gru/repos/owner/repo.git
  • Create worktree from bare repo:
    cd ~/.gru/repos/owner/repo.git
    git worktree add ~/.gru/work/owner/repo/issue-<issue#> -b issue-<issue#>
    

4. Check if Worktree Already Exists

  • Look in ~/.gru/work/owner/repo/ for existing worktree for this issue
  • If found, inform user and provide path
  • If not found, create new worktree

5. Next Steps

Inform the user:

✓ Worktree created at ~/.gru/work/owner/repo/issue-<issue#>
✓ Branch: issue-<issue#>

Next steps:
  cd ~/.gru/work/owner/repo/issue-<issue#> && gru do <issue#>
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. 2mo ago First seen · 44 lines · 12 tokens per session scan A fce972a25bb0

Subscribe to this mod's changes

setup-worktree is a command published in the GitHub repository fotoetienne/gru (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 12 tokens to every session and 367 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other commands, from other repositories

design-ship

One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…

yonatangross/orchestkit · 84 tokens

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

pr

Handle the full workflow from current branch state to an open, CI-monitored pull request.

opsmill/infrahub-mcp · 18 tokens

careful

Blocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE / TRUNCATE, kubectl delete and terraform or tofu destroy, including inside ssh remote commands, and makes Claude ask the…

yonatangross/orchestkit · 84 tokens

Checkpoint Commit

Commit changes at meaningful checkpoints throughout the workflow.

opsmill/infrahub-mcp · 11 tokens

reconcile

Establish git ground truth (branch, status, stashes, worktrees, ahead/behind) before any mutation, halt on protected or destructive operations, then carry the known-good state through a single-concern commit, a push, an open PR, and — after the PR merges — a fast-forward of the default branch. Enforces Law 1 (Research…

naimkatiman/continuous-improvement · 80 tokens