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 LuisUrrutia/skills --skill worktrunkgit clone --depth 1 https://github.com/LuisUrrutia/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/luisurrutia/skills/worktrunk)<a href="https://agentmods.dev/skills/luisurrutia/skills/worktrunk"><img src="https://agentmods.dev/badge/skills/luisurrutia/skills/worktrunk/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/luisurrutia/skills/worktrunk"><img src="https://agentmods.dev/badge/skills/luisurrutia/skills/worktrunk.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.00023 | $0.00386 |
| Opus 5 | $0.00012 | $0.00193 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
worktrunk 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 8d 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
Worktrunk
Use wt for the worktree lifecycle when it is available. Run it inside the repository.
Core workflow
wt list
wt switch --create <branch>
wt switch <branch>
wt remove
- Use
--createfor a new branch. Without it,wt switchenters an existing worktree or creates one for an existing branch. wt switchopens the picker,wt switch -returns to the previous worktree, andwt switch ^enters the default branch worktree.- Continue work in the directory reported by
wt. When shell state does not persist between commands, set the next command's working directory explicitly. - Use
wt <command> --helpfor version-specific flags. Use rawgit worktreecommands only when the user requests them orwtis unavailable.
References
Read only the reference that matches the task:
- Creating or editing
.config/wt.toml, choosing hooks, or handling hook approvals: references/project-config.md - Editing personal paths or defaults in
~/.config/worktrunk/config.toml: references/user-config.md - Using bases, shortcuts, remote branches, pull requests, or non-persistent shells with
wt switch: references/switch.md - Filtering worktrees or consuming structured
wt listoutput: references/list.md - Removing worktrees or branches, especially with force flags: references/remove.md
- Fixing setup, directory switching, hooks, or slow status collection: references/troubleshooting.md
What ships with it
6 files 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.
- 8d ago First seen · 34 lines · 23 tokens per session scan A 16b4dfc733b9
worktrunk is a skill published in the GitHub repository LuisUrrutia/skills (2 stars, last pushed 15d ago), licensed MIT. It adds 23 tokens to every session and 386 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-31.
Other skills, from other repositories
shipping-and-launch
Use when preparing to release an Android app to production. Pre-launch checklist covering code quality, security, performance, accessibility, Play Store requirements, staged rollout, and rollback planning.
git-workflow-and-versioning
Use when managing branches, commits, versioning, and release workflows for Android projects. Covers trunk-based development, atomic commits, versionCode/versionName, and signing configurations.
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…