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 instructions/coderabbitai/git-worktree-runner/completionsgit clone --depth 1 https://github.com/coderabbitai/git-worktree-runnerWhat 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.01366 | $0.01366 |
| Opus 5 | $0.00683 | $0.00683 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
git-worktree-runner completions.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Completions Instructions
Overview
Shell completions provide tab-completion for git gtr commands, flags, branches, and adapter names across Bash, Zsh, and Fish shells.
When to Update Completions
Always update all three completion files when:
- Adding new commands (e.g.,
git gtr new-command) - Adding new flags to existing commands (e.g.,
--new-flag) - Adding editor or AI adapters (completion must list available adapters)
- Changing command names or flag names
File Responsibilities
completions/gtr.bash- Bash completion (requires bash-completion v2+)completions/_git-gtr- Zsh completion (uses Zsh completion system)completions/gtr.fish- Fish shell completion
Implementation Pattern
Each completion file implements:
- Command completion - Top-level commands (
new,rm,editor,ai,list, etc.) - Flag completion - Command-specific flags (e.g.,
--from,--force,--editor) - Branch completion - Dynamic completion of git branches plus special ID
1(viagit branch) - Adapter completion - Editor names (
cursor,vscode,zed) and AI tool names (aider,claude,codex)
Testing Completions
Manual testing (no automated tests):
# Bash - source the completion file (requires git's bash completion to be loaded)
source completions/gtr.bash
git gtr <TAB> # Should show commands
git gtr new <TAB> # Should show flags
git gtr go <TAB> # Should show branches + '1'
git gtr editor <TAB> # Should show branches + '1'
git gtr editor --editor <TAB> # Should show editor names
# Zsh - copy to fpath directory and reload (requires git's zsh completion)
mkdir -p ~/.zsh/completions
cp completions/_git-gtr ~/.zsh/completions/
# Add to ~/.zshrc: fpath=(~/.zsh/completions $fpath)
# Add to ~/.zshrc: autoload -Uz compinit && compinit
exec zsh # Reload shell
git gtr <TAB> # Should show commands
git gtr new <TAB> # Should show flags
git gtr go <TAB> # Should show branches + '1'
# Fish - symlink to ~/.config/fish/completions/
ln -s "$(pwd)/completions/gtr.fish" ~/.config/fish/completions/
exec fish # Reload shell
git gtr <TAB> # Should show commands
git gtr new <TAB> # Should show flags
git gtr go <TAB> # Should show branches + '1'
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.
- yesterday First seen · 145 lines · 1,366 tokens per session scan A df64af14c284
git-worktree-runner completions.instructions.md is an instructions file published in the GitHub repository coderabbitai/git-worktree-runner (1,754 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,366 tokens to every session, about $0.0068 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 instructions, from other repositories
mulmoterminal CLAUDE.md
Instructions for receptron/mulmoterminal, covering claude.md — mulmoterminal, stack & package manager, run after changes, import a component at module scope, never inside a test and no emojis.
operator-oss CLAUDE.md
Instructions for iishyfishyy/operator-oss, covering claude.md, commands, architecture, the turn lifecycle (core flow) and key modules (by responsibility).
vibe-tree CLAUDE.md
Instructions for sahithvibudhi/vibe-tree, covering claude instructions, github actions failed build logs, electron app startup issues, launch with project and pull requests.
CommandMate CLAUDE.md
Instructions for Kewton/CommandMate, covering claude.md, ⚠️ 重要: モジュール詳細を claude.md に書かないこと, プロジェクト概要, 基本情報 and 技術スタック.
vscode-ext-tmux-worktree AGENTS.md
Instructions for kargnas/vscode-ext-tmux-worktree, covering ai agent guidelines, instruction, tested vs code, 1. codebase understanding and project structure.
CommandMate AGENTS.md
Instructions for Kewton/CommandMate, covering agents.md, scope, project context, working principles and coding rules.