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/tx1207/hello-scholar/using-git-worktreesnpx skills add Tx1207/hello-scholar --skill using-git-worktreesgit clone --depth 1 https://github.com/Tx1207/hello-scholarWhat 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.00043 | $0.01956 |
| Opus 5 | $0.00022 | $0.00978 |
| Sonnet 5 | $0.00009 | $0.00391 |
| Haiku 4.5 | $0.00004 | $0.00196 |
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 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.
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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Entry Gate
Enter only with one of these explicit authorizations:
- Explicit user request: The user clearly asks for a Git worktree or an isolated workspace.
- Approved Task requirement: An Approved Task explicitly says to use a Worktree Process.
- Approved risk recommendation: The Agent states a concrete isolation risk, such as changing a user-dirty checkout or a branch used by parallel work, and the user explicitly approves the recommendation.
An ordinary Plan, Task, Feature, or Validation label is not authorization. If none applies, return to the current Task flow without running Git commands from this skill. Do not ask about or create a worktree merely because the work is implementation-shaped.
For a concrete risk recommendation that has not yet been approved, state the specific risk and ask whether to prepare an isolated worktree. Wait for an explicit answer. Approval activates authorization 3; a refusal returns to the current Task flow without creation.
An explicit user request, an Approved Task requirement, and an approved risk recommendation already provide creation consent. Do not ask one of these paths for the same consent again.
When authorized, prepare an isolated Git workspace. Core order: Detect existing isolation first -> choose mechanism -> prepare -> verify.
Scope and Exit
This skill ends when an isolated workspace is usable and its baseline status is known. It does not implement the feature, commit, merge, clean up, or remove a worktree.
After this skill exits, follow the current AGENTS and Task requirements for implementation and verification. No-worktree, declined isolation, or a blocked creation never waives required tests. Cleanup requires separate explicit authorization and real provenance for the workspace and branch.
Step 0: Detect Existing Isolation
Run this step only after the Entry Gate authorizes isolation. Before creating anything, capture the repository topology and source-checkout state:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 175 lines · 43 tokens per session scan A c978f8678383
using-git-worktrees is a skill published in the GitHub repository Tx1207/hello-scholar (5 stars, last pushed 21d ago), licensed MIT. It adds 43 tokens to every session and 1,956 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.