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/timvw/wt/wtnpx skills add timvw/wt --skill wtgit clone --depth 1 https://github.com/timvw/wtWhat 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.00081 | $0.02918 |
| Opus 5 | $0.00041 | $0.01459 |
| Sonnet 5 | $0.00016 | $0.00584 |
| Haiku 4.5 | $0.00008 | $0.00292 |
Grade A, and why
wt 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 today.
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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with wt - Git Worktree Manager
wt is a fast Git worktree helper written in Go. It wraps git worktree with a convenient interface, organized directory structure, and smart defaults. Each branch gets its own directory — no stashing, no branch switching.
Core Philosophy
Never switch branches in the main checkout. Always create a worktree for each task. This keeps the user's workspace clean and allows parallel work on multiple branches.
Commands
| Command | Purpose |
|---|---|
wt clone <owner/repo|url> [dest] |
Clone a repo under repo_root (host/owner/repo/branch), on its default branch |
wt create <branch> [base] |
Create a new branch in a worktree (defaults to main/master as base) |
wt co <branch> |
Checkout an existing branch in a new worktree |
wt co |
Interactive: fuzzy-search from available branches |
wt cd <branch> |
Switch to an existing worktree (alias: wt sw); never creates one |
wt cd |
Interactive: fuzzy-search from existing worktrees |
wt ls |
List all worktrees |
wt rm <branch> |
Remove a worktree |
wt rm |
Interactive: fuzzy-search worktree to remove |
wt pr [number|url] |
Checkout a GitHub PR (requires gh CLI) |
wt pr |
Interactive: fuzzy-search from open PRs |
wt mr [number|url] |
Checkout a GitLab MR (requires glab CLI) |
wt mr |
Interactive: fuzzy-search from open MRs |
wt status |
Color-coded overview of all worktrees |
wt status --ci |
Include CI/CD pipeline status per branch |
wt copy [branch] |
Materialise the [files] set into a worktree (--dry-run, --force, --from) |
wt info |
Show active strategy, pattern, variables |
wt config show |
Show effective config with sources |
wt cleanup --stale |
Detect stale worktrees (deleted remotes, inactive commits) |
wt prune |
Clean up stale worktree admin files |
wt migrate |
Migrate worktrees to match configured paths |
wt init |
Configure shell integration |
wt examples |
Show practical examples |
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.
- today First seen · 227 lines · 81 tokens per session scan A 757561eece2a
wt is a skill published in the GitHub repository timvw/wt (55 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 2,918 once invoked, about $0.0004 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-09-01.
Other skills, from other repositories
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
cabloy-worktree-environment
This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup. It prepares a confirmation-gated, worktree-local Vona and Zova runtime environment for a linked Cabloy Basic or Cabloy Start Git worktree using Git…
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…