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/marmot-protocol/agent-config/create-git-worktreegit clone --depth 1 https://github.com/marmot-protocol/agent-configWhat 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.00008 | $0.00359 |
| Opus 5 | $0.00004 | $0.00179 |
| Sonnet 5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
create-git-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 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.
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.
What it actually says
Create Git Worktree
Create a new git worktree in the trees/ directory with the branch name provided as the argument.
CRITICAL: This is a ONE-SHOT command
- DO NOT ask any questions - use
$ARGUMENTSas the branch name directly - The branch name IS the argument - no clarification needed
- Execute all steps automatically without prompting
Execution Steps
1. Get Branch Name
The branch name is: $ARGUMENTS
If $ARGUMENTS is empty, report an error: "Usage: /create-git-worktree "
2. Create Worktree Directory
mkdir -p trees
3. Create the Worktree
Run this command from PROJECT_CWD:
git worktree add trees/$ARGUMENTS -b $ARGUMENTS 2>/dev/null || git worktree add trees/$ARGUMENTS $ARGUMENTS
This handles both cases:
- If the branch doesn't exist: creates it with
-b - If the branch already exists: checks it out in the worktree
4. Verify Creation
git worktree list | grep "trees/$ARGUMENTS"
5. Switch to the Worktree
This is essential - change into the new worktree directory:
cd trees/$ARGUMENTS
6. Confirm Ready
Report success with the current working directory and branch:
pwd
git branch --show-current
Tell the user they are now in the worktree and ready to work.
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 · 65 lines · 8 tokens per session scan A e1d9d043ffac
create-git-worktree is a command published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 359 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-31.
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.