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/tmchow/agent-skills/clawpatchnpx skills add tmchow/agent-skills --skill clawpatchgit clone --depth 1 https://github.com/tmchow/agent-skillsWhat 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.00158 | $0.03515 |
| Opus 5 | $0.00079 | $0.01758 |
| Sonnet 5 | $0.00032 | $0.00703 |
| Haiku 4.5 | $0.00016 | $0.00351 |
Grade C, and why
clawpatch scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
(`[ -d .clawpatch ] && rm -r .clawpatch` — guarded, never `rm -rf`) is a last How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clawpatch — agent workflow
Clawpatch (
openclaw/clawpatch, https://clawpatch.ai) is an agent-driven CLI: it reviews a repo into structured findings and can apply validated per-finding fixes. It needs Node.js 22+ and a provider CLI (codex by default);fixrefuses dirty source worktrees by default, whilereview/ci/revalidatecan include dirty code when explicitly scoped.This skill is judgment + orchestration, not a CLI reference. For exact flags, JSON fields, and exit codes, trust
clawpatch <cmd> --helpand the live--jsonoutput over anything written here — Clawpatch is pre-1.0 and its surface drifts, so a written copy will mislead. What this skill carries is what--helpcan't tell you: when to reach for it, how to fix findings in parallel, and the traps.
When to use
Use Clawpatch when the user names it, or wants whole-repo automated review that yields locatable findings plus optional validated fixes.
Don't use it for: a small diff already under review (a whole-repo review cycle
is overkill — use a diff-review tool); a bug the user already understands and
just wants written; or when no provider CLI (codex/claude/cursor/grok/
opencode/pi/acpx, or mock for tests) is installed — clawpatch doctor
fails fast, so say so and stop.
Setup
clawpatch doctor verifies the install and the provider. The published CLI
requires Node.js 22+. If clawpatch is missing, install the current published
package (npm install -g [email protected]). The provider (codex by default) is
the user's to install and authenticate — don't run login flows on their behalf.
Gitignore .clawpatch/ early to keep status, commits, and PR diffs clean.
Clawpatch allows its own state directory to change during runs; fix's dirty
guard is for source worktree changes, not .clawpatch/ churn. Add the single
line .clawpatch/ before review/fix when the repo doesn't already ignore it,
but remember .gitignore is tracked — confirm with the user before editing it.
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 · 258 lines · 158 tokens per session scan C a61c8b3bc0b5
clawpatch is a skill published in the GitHub repository tmchow/agent-skills (64 stars, last pushed 16d ago), licensed MIT. It adds 158 tokens to every session and 3,515 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
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.