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 skills add maxedapps/agent-skills --skill use-worktreesgit clone --depth 1 https://github.com/maxedapps/agent-skillsWrote 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.
[](https://agentmods.dev/skills/maxedapps/agent-skills/use-worktrees)<a href="https://agentmods.dev/skills/maxedapps/agent-skills/use-worktrees"><img src="https://agentmods.dev/badge/skills/maxedapps/agent-skills/use-worktrees/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.
<a href="https://agentmods.dev/skills/maxedapps/agent-skills/use-worktrees"><img src="https://agentmods.dev/badge/skills/maxedapps/agent-skills/use-worktrees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00065 | $0.00652 |
| Opus 5.5 | $0.00026 | $0.00261 |
| Sonnet 5.5 | $0.00013 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
use-worktrees 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use git worktrees
Create
Worktrees live only in ~/worktrees/<repo-dir>/<branch-slug> (branch name with / → -). Create them with Git:
git worktree add ~/worktrees/<repo-dir>/<branch-slug> -b <branch> <target-branch>
For an existing branch, such as an open PR, run git fetch origin <branch>:<branch> and drop -b. Inside herdr (HERDR_ENV=1), don't use herdr worktree create: it opens a separate workspace. Open the worktree in a new pane of your current workspace instead:
herdr pane split --current --direction right --cwd <worktree-path> --no-focus
Tag the new pane as your worker, with its id from the split's reply (result.pane.pane_id), so agentmanager shows it under you:
herdr pane report-metadata <new-pane-id> --source agentmanager --token parent=$HERDR_PANE_ID
Then set it up: install dependencies and copy ignored config such as .env from the main checkout. Give concurrent worktrees their own deployment stage; never let parallel checkouts mutate the same deployment state.
Sync
- Merge the target branch into the worktree branch (
git merge <target-branch>) at checkpoints and before touching anything parallel work may have changed. Never rebase or rewrite shared branches. - Run the full check suite after every sync.
- Migrations: if the target took a migration number this branch also uses, renumber this branch's migration, even without a textual conflict.
- Lockfiles: keep both sides' manifest changes and regenerate the lockfile; never hand-edit it.
Finish
Do a final sync, get the checks green, push, and open a pull request. Never merge into the target branch yourself; that happens on the PR, when the user asks. No force-push, no bulk --theirs/--ours resolutions.
Cleanup
Whoever created a worktree removes it; an agent working inside one leaves it alone. Once everything is committed, pushed, and in an open PR, remove it right away; later reviews or fixes use a fresh worktree.
git worktree remove <path>
git branch -d <branch>
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.
- 1mo ago Changed · +6 lines 027e0acbc7d1
- 1mo ago Changed · -7 lines · +3 tokens per session dc26a273c172
- 1mo ago Changed · -2 lines · -11 tokens per session 783059718c56
- 2mo ago First seen · 64 lines · 73 tokens per session scan A c1d66d550f8c
use-worktrees is a skill published in the GitHub repository maxedapps/agent-skills (60 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 652 once invoked, about $0.0003 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.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.