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-disknpx skills add lifedever/skills-plugin --skill mac-cleanup-diskgit 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-disk)<a href="https://agentmods.dev/skills/lifedever/skills-plugin/mac-cleanup-disk"><img src="https://agentmods.dev/badge/skills/lifedever/skills-plugin/mac-cleanup-disk.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.00173 | $0.01856 |
| Opus 5 | $0.00086 | $0.00928 |
| Sonnet 5 | $0.00035 | $0.00371 |
| Haiku 4.5 | $0.00017 | $0.00186 |
Grade D, and why
mac-cleanup-disk scanned grade D with 2 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 5d 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.
| `mo touchid` | Configure sudo Touch ID | △ | - | Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Hand the result to the user; they decide whether to run `mo purge` or `rm -rf` specific directories manually. How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mac-cleanup-disk
A macOS maintenance workflow based on tw93/mole. Iron rule: preview first, confirm, then execute. Any deletion requires explicit user text confirmation.
0. Pre-flight Check
Before any workflow, verify mole is installed:
which mo && mo --version
If it isn't installed, don't proactively brew install — report "mole not installed, requires brew install mole. Proceed?" and wait for the user to agree before installing.
1. First Step After a Request: Clarify the Mode
Don't jump in just because the user said "clean my Mac". Lay out the 4 modes first:
| # | Mode | When to use | Main commands |
|---|---|---|---|
| 1 | 💨 Daily clean | Periodic maintenance, clear caches and logs | mo clean --dry-run → mo clean |
| 2 | 🔍 Deep clean | Disk space tight, thorough sweep | mo analyze + mo clean + mo installer + mo optimize |
| 3 | 💻 Developer clean | Clean node_modules / target / venv, etc. |
mo purge |
| 4 | 🩺 Smart diagnosis | Not sure what to clean — look at data first | mo status + mo analyze + mo clean --dry-run |
If the user already knows which command they want ("I just want to run mo clean"), skip this step and go straight to the safety flow.
2. TUI Restrictions (important!)
The following mole subcommands are full-screen TUI interactive programs. Running them via Claude Code's Bash tool will hang, show no content, and refuse keypresses:
mo(no-args main menu)mo analyzemo uninstallmo purgemo installermo status
Handling principle: let the user run these in their own terminal. The AI must not run them on the user's behalf, and must not timeout-then-kill. The AI's role is:
- Help interpret the TUI output (user screenshots or pastes text back)
- Run non-TUI commands on the user's behalf:
mo clean --dry-run,mo clean,mo optimize --dry-run,mo optimize,df -h
3. Safety Rules (non-negotiable)
- Destructive operations must be preceded by
--dry-run: includesmo clean,mo optimize,mo uninstall,mo purge,mo installer - After the dry-run output, wait for user text reply like "go / continue / confirm / OK" before running the real version — verbal consent counts, silence does not
- Before deep clean, ask: "Have you saved important work? Are dev projects committed?" mole won't touch those, but in case the user picked a destructive mode by mistake
- Stop on error: any non-zero exit from a mo command — report the error immediately, do not retry / do not work around / do not swap commands. Could be a mole bug or permission issue, needs the user's judgment.
- Never proactively run
mo uninstall,mo purge— these may delete files the user is actively using; the user must hand-pick items in the TUI
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.
- 5d ago First seen · 139 lines · 173 tokens per session scan D 000ba197c571
mac-cleanup-disk is a skill published in the GitHub repository lifedever/skills-plugin (11 stars, last pushed 13d ago), licensed MIT. It adds 173 tokens to every session and 1,856 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…