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 saski/arnesto --skill git-worktreesgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/git-worktrees)<a href="https://agentmods.dev/skills/saski/arnesto/git-worktrees"><img src="https://agentmods.dev/badge/skills/saski/arnesto/git-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/saski/arnesto/git-worktrees"><img src="https://agentmods.dev/badge/skills/saski/arnesto/git-worktrees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00033 | $0.00336 |
| Opus 5.5 | $0.00013 | $0.00134 |
| Sonnet 5.5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
git-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.
This is a copy
100% identical to git-worktrees — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Git Worktrees
Directory Convention
Worktrees live in a sibling directory named <project>_worktrees:
parent/
├── myproject/ # main repo
└── myproject_worktrees/ # worktrees directory
├── feature_1/
└── feature_2/
Branch Naming
Use <feature>_<N> pattern when creating multiple worktrees:
auth-refactor_1,auth-refactor_2api-migration_1,api-migration_2
Workflow
- Get project name from current directory
- Create worktrees directory if needed:
../<project>_worktrees/ - Create worktree with new branch:
git worktree add <path> -b <branch>
Creating Multiple Worktrees
When asked for N worktrees for a feature:
PROJECT=$(basename "$PWD")
WORKTREES_DIR="../${PROJECT}_worktrees"
mkdir -p "$WORKTREES_DIR"
for i in $(seq 1 N); do
git worktree add "${WORKTREES_DIR}/<feature>_${i}" -b "<feature>_${i}"
done
Cleanup
Remove worktree and branch:
git worktree remove <path>
git branch -d <branch>
List all worktrees: git worktree list
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 First seen · 55 lines · 33 tokens per session scan A 5a9679236bca
git-worktrees is a skill published in the GitHub repository saski/arnesto (6 stars, last pushed 5d ago), licensed Unlicense. It adds 33 tokens to every session and 336 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-worktrees, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
issue-triage
Sort a backlog of issues and pull requests: label each by type and severity, link duplicates, try the bug reports, ask for the one missing detail, and turn the accepted ones into ready-to-work briefs.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
pr-explainer
Use when a developer asks to explain a pushed PR, walk through a PR stack, understand one stack member, or explain what an AI agent just pushed so they can connect code changes to end-to-end functionality and update domain knowledge. Not for defect review, merge approval, PR-body authoring, or full-repository…