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 skills/raidriar7170/hermes-skilleval/using-git-worktreesnpx skills add Raidriar7170/hermes-skilleval --skill using-git-worktreesgit clone --depth 1 https://github.com/Raidriar7170/hermes-skillevalWrote 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/raidriar7170/hermes-skilleval/using-git-worktrees)<a href="https://agentmods.dev/skills/raidriar7170/hermes-skilleval/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/raidriar7170/hermes-skilleval/using-git-worktrees.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00285 |
| Opus 5 | $0.00011 | $0.00143 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
Using 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 5d 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.
What it actually says
Using Git Worktrees
Use when implementation should be isolated from the main checkout or when multiple agents may work at once. Confirm the directory, branch, and git status before editing, then keep changes scoped to the assigned task.
Evidence
- Worktree path and branch.
- Initial git status.
- Changed files limited to the assignment.
Source Snapshot
Source: superpowers/using-git-worktrees/SKILL.md
Short excerpt used for provenance, not a full source copy.
# Using Git Worktrees ## Overview Ensure work happens in an isolated workspace. Prefer
your platform's native worktree tools. Fall back to manual git worktrees only when no
native tool is available. **Core principle:** Detect existing isolation first. Then use
native tools. Then fall back
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.
- 5d ago First seen · 36 lines · 22 tokens per session scan A 3875b0fb894a
Using Git Worktrees is a skill published in the GitHub repository Raidriar7170/hermes-skilleval (124 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 285 once invoked, about $0.0001 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 skills, from other repositories
codspeed-optimize
Autonomously optimize code for performance using CodSpeed benchmarks, flamegraph analysis, and iterative improvement. Use this skill whenever the user wants to make code faster, reduce CPU usage, optimize memory, improve throughput, find performance bottlenecks, or asks to 'optimize', 'speed up', 'make faster'…
codspeed-setup-harness
Set up performance benchmarks and CodSpeed harness for a project. Use this skill whenever the user wants to create benchmarks, add performance tests, set up CodSpeed, configure codspeed.yml, integrate a benchmarking framework (criterion, divan, pytest-benchmark, vitest bench, go test -bench, google benchmark), or when…
custom-agent-creator
Create and integrate new modular agents for browseruse-bench (BaseAgent in browserusebench/agents/, registry import in init.py, entry in configs/agentregistry.yaml, runtime config in root config.yaml agents section). Use when a user asks to add/register a new agent, scaffold a custom agent, or implement a new agent…
bubench-run
Use this skill whenever the user describes a benchmark experiment using any combination of these parameters — agent (e.g. browser-use, skyvern), model (e.g. deepseek, minimax, claude, gemini, gpt), data/benchmark (e.g. LexBench-Browser), browser (e.g. Chrome-Local, lexmount), and tasks (specific IDs or "all"). Trigger…
pr-unresolved-solutions
Draft and track fixes for unresolved PR review threads. Use when you need to generate a solution draft markdown for the latest/current PR unresolved threads and keep .pr/ /reviewchecklist.md plus .pr/ /unresolvedchecklist.md checkbox states synchronized as issues are fixed.
docs-update
Update Mintlify documentation in docs/ for browseruse-bench, including adding new pages, enforcing .mdx files, and keeping English/Chinese navigation parity. Use when adding or editing docs pages, fixing missing/incorrect language variants, or updating docs/docs.json navigation.