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/jjmartres/ai-coding-agents/worktrunknpx skills add jjmartres/ai-coding-agents --skill worktrunkgit clone --depth 1 https://github.com/jjmartres/ai-coding-agentsWrote 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/jjmartres/ai-coding-agents/worktrunk)<a href="https://agentmods.dev/skills/jjmartres/ai-coding-agents/worktrunk"><img src="https://agentmods.dev/badge/skills/jjmartres/ai-coding-agents/worktrunk.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.00135 | $0.01876 |
| Opus 5 | $0.00068 | $0.00938 |
| Sonnet 5 | $0.00027 | $0.00375 |
| Haiku 4.5 | $0.00014 | $0.00188 |
Grade B, and why
worktrunk scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Add to `~/.claude/settings.json` for statusline: How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktrunk Skill
Worktrunk (wt) is a CLI for git worktree management designed to run AI agents
(like Claude Code) in parallel across isolated branches. Think of it as making
git worktree as easy as git branch.
Quick Reference
| Task | Command |
|---|---|
| Create worktree + switch | wt switch --create feat |
| Create worktree + launch Claude | wt switch --create feat -x claude |
| List all worktrees | wt list |
| Merge & clean up | wt merge main |
| Remove current worktree | wt remove |
| Commit staged changes | wt step commit |
Installation
# macOS/Linux (recommended)
brew install worktrunk && wt config shell install
# Cargo
cargo install worktrunk && wt config shell install
# Windows
winget install max-sixty.worktrunk
git-wt config shell install
Shell integration (wt config shell install) is required so that wt switch
can actually change the shell's directory.
Core Workflow
1. Create and Switch
wt switch --create feature-auth # New branch + worktree
wt switch --create feature-auth -x claude # + launch Claude in it
wt switch existing-branch # Switch to existing worktree
wt switch - # Previous worktree
Worktrees are placed at ../repo.branch-name by default (configurable).
2. Inspect Status
wt list # All worktrees with status, commits, CI
wt list --full --branches # Include remote branches without worktrees
wt list --format=json # Machine-readable output
Key indicators in wt list:
@= current worktree+/-= staged / unstaged changes↑/↓= ahead / behind remote⇡/⇣= ahead / behind default branch🤖= Claude is working (Claude Code plugin)💬= Claude waiting for input
What ships with it
2 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.
- 4d ago First seen · 253 lines · 135 tokens per session scan B b76c420bb1bb
worktrunk is a skill published in the GitHub repository jjmartres/ai-coding-agents (43 stars, last pushed 2mo ago), licensed MIT. It adds 135 tokens to every session and 1,876 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
audit
Eight audit modes (codebase — owns "audit the codebase" — docs/process, performance, threat-model, motion, SEO, debt). Triggers "nuclear review", "whole codebase review", "adversarial audit", "fable audit", "correctness audit", "audit the docs", "doc drift", "process audit", "perf audit", "why is it slow", "bundle…
autoresearch
Autonomous skill-prompt optimization — Karpathy-style mutate/score/keep loop on SKILL.md. Triggers "autoresearch", "optimize skill", "tune", "evolve" a skill, "prompt optimization".
ship
Verify and publish by pushing, opening a PR, and watching CI; land mode merges then cleans branches. Triggers "ship it", "create PR", "/ship", "watch the PR", "babysit CI"; land mode "land it", "/ship land", "fix CI and merge".
oracle
Expert agent in advice, risk, or weighted-comparison mode. Triggers "what should I", "advice on"; "what could go wrong", "risks", "premortem"; or "compare approaches", "which is better", "trade-off analysis", "tech selection".