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/motlin/claude-code-plugins/wipnpx skills add motlin/claude-code-plugins --skill wipgit clone --depth 1 https://github.com/motlin/claude-code-pluginsWhat 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.00134 | $0.02187 |
| Opus 5 | $0.00067 | $0.01094 |
| Sonnet 5 | $0.00027 | $0.00437 |
| Haiku 4.5 | $0.00013 | $0.00219 |
Grade A, and why
wip 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wip — work-in-progress cleanup pipeline
Drive a repo full of leftover worktrees and half-finished branches toward a clean, landed state. The pipeline has four phases that run in order, each gated:
- Worktrees — remove every worktree except the main one and protected ones, freeing their branches for rebase.
- Rebase + GC — rebase every branch onto the upstream main (
j g/git-all), deleting branches that have merged. - Test — re-test the rebased commits (rebasing invalidates prior test results).
- Push — push the green branches; the user opens/merges PRs.
These four phases are the bulk-cleanup core of a longer idea → merged-PR lifecycle (the later stages — open PR, CI, review, merge — are the user's call). If the repo or user documents a WIP state model, follow it for those later stages.
Golden rules (read before doing anything)
- Never
--force. Worktree removal usesgit worktree remove --no-force(write the flag explicitly); pushes usegit push --force-with-lease. Git's refusal to act is the safety net that protects uncommitted work and unexpected remote changes — don't defeat it. - The worktree/branch set is a moving target. In an active repo, worktrees and branches get
created, switched, and merged while you work (often by other agents or the user). Recompute
the live set with
git worktree list --porcelain/git for-each-refimmediately before each action — never trust a snapshot from a minute ago. Re-git fetchbefore testing and pushing. - Gate the irreversible, outward-facing steps. Removing a worktree with WIP, force-pushing,
and
delete-merged(which deletes remote branches) are hard to undo. Surface them and get the user's OK rather than charging ahead. Until the flow is proven smooth in a given repo, prefer asking at each phase boundary. - Work in dedicated worktrees, keep the main checkout clean. Rebases and tests check out
commits; doing that in the user's main worktree disrupts them and leaves it detached/mid-rebase.
Isolate each in its own throwaway worktree (
git worktree add), then tear it down.
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 · 143 lines · 134 tokens per session scan A 92a2e018fe99
wip is a skill published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 134 tokens to every session and 2,187 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…