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/samuelclay/newsblur/worktreegit clone --depth 1 https://github.com/samuelclay/NewsBlurWhat 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.00009 | $0.00264 |
| Opus 5 | $0.00005 | $0.00132 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
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 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.
What it actually says
Your task
Create a new git worktree for the branch specified in the arguments and start the development environment.
Arguments provided: {{ arguments }}
Steps to execute
-
Parse the branch name from the arguments (the first word)
-
Create the worktree using auto-detect logic (try new branch first, fall back to existing):
BRANCH_NAME="<parsed-branch-name>" git worktree add ".worktree/${BRANCH_NAME}" -b "${BRANCH_NAME}" 2>/dev/null || \ git worktree add ".worktree/${BRANCH_NAME}" "${BRANCH_NAME}" -
Change the working directory to the new worktree:
cd ".worktree/${BRANCH_NAME}" -
Run worktree-dev.sh to start the development environment:
./worktree-dev.sh -
Report success including:
- The workspace URL (from worktree-dev.sh output)
- That the working directory is now
.worktree/<branch-name> - Available commands:
make worktree-log,make worktree-close
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 · 36 lines · 9 tokens per session scan A 485964035d2e
worktree is a command published in the GitHub repository samuelclay/NewsBlur (7,600 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 264 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.
Other commands, from other repositories
release-mobilewright
Prepare a mobilewright release by updating CHANGELOG.md with the next patch version.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
mobile-checkpoint
Save and restore mobile development checkpoints. Capture build variants, test states, and project state before risky operations.
platform-info
Detect project type (Android/iOS/KMP), list platforms, show platform info, and delegate to appropriate commands.
ios-test
Run iOS tests with xcodebuild, show coverage. Invokes ios-testing patterns.
mobile-test
Unified mobile test command. Detects platform (Android/iOS/KMP) and delegates to appropriate test command.