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/wbern/agent-instructions/worktree-addgit clone --depth 1 https://github.com/wbern/agent-instructionsWhat 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.00024 | $0.04362 |
| Opus 5 | $0.00012 | $0.02181 |
| Sonnet 5 | $0.00005 | $0.00872 |
| Haiku 4.5 | $0.00002 | $0.00436 |
Grade B, and why
worktree-add scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
<destination>${parent_path}/${branch_name}/.claude/settings.local.json</destination> How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Setup
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
User arguments:
Worktree-add: $ARGUMENTS
End of user arguments
<current_state>
Current branch: git branch --show-current
Current worktrees: git worktree list
Remote branches: git branch -r
Uncommitted changes: git status --short
</current_state>
<execution_steps> <step_0> Ask user for setup mode How would you like to set up the worktree? Quick Just create the worktree (skip deps, settings, IDE) Full setup Install dependencies, copy settings, open in IDE <set_variable>$SETUP_MODE = user selection ("quick" or "full")</set_variable> Allow quick worktree creation when user just needs the branch </step_0>
<step_0b> Detect git hosting provider and available tools (only needed if argument is an issue URL) Only run this step if first argument looks like a git hosting URL
<detect_provider> <check_remote_url>git remote get-url origin</check_remote_url> <identify_host> - github.com → GitHub - gitlab.com → GitLab - bitbucket.org → Bitbucket - Other → Ask user </identify_host> </detect_provider> <check_available_tools> <list_mcp_servers>Check which git-hosting MCP servers are available (github, gitlab, etc.)</list_mcp_servers> <check_cli>Check if gh/glab CLI is available as fallback</check_cli> </check_available_tools> <select_tool> <if_single_mcp>If only one relevant MCP available, confirm with user</if_single_mcp> <if_multiple>Let user choose which tool to use</if_multiple> <if_told_earlier>If user specified tool earlier in conversation, use that without asking again</if_told_earlier> <store_as>$GIT_HOST_TOOL (e.g., "github_mcp", "gitlab_mcp", "gh_cli")</store_as> </select_tool>
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 · 378 lines · 24 tokens per session scan B 9bfebfd4cbd9
worktree-add is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 4,362 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.