Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Jerry0022/dotclaudenpx agentmods add skills/jerry0022/dotclaude/mcp-reapWrote 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/jerry0022/dotclaude/mcp-reap)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/mcp-reap"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/mcp-reap/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/jerry0022/dotclaude/mcp-reap"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/mcp-reap.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.00029 | $0.00918 |
| Opus 5 | $0.00015 | $0.00459 |
| Sonnet 5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
mcp-reap 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Reap
Reclaims orphaned Claude Desktop MCP server child processes — leftovers from previously-closed sessions that were never reliably terminated and linger, accumulating RAM. Driven by two hooks so it runs both once per session and periodically thereafter, without requiring a restart:
hooks/session-start/ss.mcp.reap.js— fires once, everySessionStart.hooks/stop/stop.mcp.reap.js— fires onStop(end of a response turn), gated by a ~20-minute per-worktree cooldown so it doesn't scan every turn. The cooldown marker uses the same atomic write-temp-then- rename pattern asself-calibration, keyed to an md5 hash ofprocess.cwd()inos.tmpdir().
Both hooks spawn scripts/mcp-reap.js --apply --json detached,
fire-and-forget, windowless ({ detached: true, stdio: 'ignore', windowsHide: true } + .unref()) and exit immediately — reaping never
delays a session start or a response turn.
Safety model
The scan-and-kill logic lives in hooks/lib/mcp-reaper.js (fully unit
tested, 46/46 in mcp-reaper.test.js) and is Windows-only — the
dead-parent-PID orphan signal only means anything on Windows, so the module
is a documented no-op on macOS/Linux. A process is only ever a reap
candidate when it matches an MCP-server launcher signature, its parent PID
is confirmed dead, AND it falls outside the live-Claude census (every
currently-live claude/claude.exe process plus its full descendant
subtree) and the caller's own process subtree — an empty/unbuildable census
means "protection unknown" and refuses to produce any candidates at all.
Every candidate is re-validated against a fresh process snapshot immediately
before both the SIGTERM and any SIGKILL escalation (TOCTOU-safe), so a pid
reused for something else between scan and kill is skipped, never touched.
The reap() module itself defaults to dry-run — nothing is ever terminated
unless a caller explicitly passes --apply; both hooks opt into it
deliberately, on the reasoning that a leaked orphan is safe to reclaim
automatically once the safety net above holds. Any enumeration or kill
failure fails safe (skip, never throw).
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.
- 9d ago First seen · 74 lines · 29 tokens per session scan A 05ae761f8dd4
mcp-reap is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 918 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…