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/lifedever/skills-plugin/mac-cleanup-processnpx skills add lifedever/skills-plugin --skill mac-cleanup-processgit clone --depth 1 https://github.com/lifedever/skills-pluginWrote 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/lifedever/skills-plugin/mac-cleanup-process)<a href="https://agentmods.dev/skills/lifedever/skills-plugin/mac-cleanup-process"><img src="https://agentmods.dev/badge/skills/lifedever/skills-plugin/mac-cleanup-process.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.00162 | $0.00948 |
| Opus 5 | $0.00081 | $0.00474 |
| Sonnet 5 | $0.00032 | $0.00190 |
| Haiku 4.5 | $0.00016 | $0.00095 |
Grade B, and why
mac-cleanup-process 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Kill denied (permissions) | Suggest `sudo`, but **don't** sudo on the user's behalf | How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mac-cleanup-process
A skill for diagnosing macOS zombie processes — pure diagnostic mode. Never proactively kills any process.
Execution Flow After Trigger
Step 1: Run the scan script
bash "${CLAUDE_SKILL_DIR}/scan.sh"
The script:
- Prints a full Markdown report to stdout
- Tees it to
~/Downloads/mac-cleanup-process-<timestamp>.md - Exits 0 on success, 1 on failure with diagnostics to stderr
Step 2: Present the report
Paste the stdout Markdown content to the user verbatim. A line or two of contextual observation is OK (e.g. pointing out the "most suspicious"), but:
- Never modify / fabricate / omit factual data in the report (PID, etime, command)
- Never add candidates from your own
ps | grepthat the script didn't surface - If the script outputs "🎉 no zombies found", just report all-clear and stop
Step 3: Wait for user instruction
Handle per this table:
| User reply | Claude action | Second confirmation? |
|---|---|---|
| No reply / "ok" / "got it" | Do nothing | - |
| "run explicit-orphan cleanup" / "one-click cleanup" | Run all kill commands from the "Explicit Orphans" section of the suggested-commands block | No (the report already labels these as "safe to nuke") |
kill <PID1> <PID2> (space or comma separated) |
Kill each one; skip and continue if a PID is missing | No |
| "clean everything" / "clean all suspicious" or other vague instructions | Ask back: "Do you mean including these suspicious items [list]?" | Yes |
| "dry run" / "look only" | Reiterate "the skill is diagnostic-only by design" | - |
Step 4: Post-kill verification
After an actual kill:
sleep 2to let the kernel reapps -p <PID>to confirm the target has exited- Brief report (before/after memory comparison, cite
vm_stat's compressor number) - Don't auto-rescan (the user will say so if they want another scan)
Step 5: Error handling
| Situation | Action |
|---|---|
scan.sh exits 1 |
Paste stderr verbatim, don't patch with your own ps |
| Killed PID no longer exists | Report "PID X has exited (possibly reaped along with the parent you just killed)", continue |
| Kill denied (permissions) | Suggest sudo, but don't sudo on the user's behalf |
| Downloads write fails | Report to the conversation as usual, warn "Not persisted this run: " |
What ships with it
3 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 · 71 lines · 162 tokens per session scan B d5fc64f4c0fc
mac-cleanup-process is a skill published in the GitHub repository lifedever/skills-plugin (11 stars, last pushed 13d ago), licensed MIT. It adds 162 tokens to every session and 948 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…