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 skills add Mateeb11/skills --skill mac-disk-cleanupgit clone --depth 1 https://github.com/Mateeb11/skillsWrote 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/mateeb11/skills/mac-disk-cleanup)<a href="https://agentmods.dev/skills/mateeb11/skills/mac-disk-cleanup"><img src="https://agentmods.dev/badge/skills/mateeb11/skills/mac-disk-cleanup/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/mateeb11/skills/mac-disk-cleanup"><img src="https://agentmods.dev/badge/skills/mateeb11/skills/mac-disk-cleanup.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.00166 | $0.01523 |
| Opus 5.5 | $0.00066 | $0.00609 |
| Sonnet 5.5 | $0.00033 | $0.00305 |
| Haiku 4.5 | $0.00017 | $0.00152 |
Grade D, and why
mac-disk-cleanup 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 1mo 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.
- App Store apps and anything root-owned need the user's password — you can't `sudo` non-interactively. Tell the user to run `! sudo rm -rf "<path>"` themselves (the `!` prefix runs it in-session so the password prompt w Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Some files are read-only; if `rm -rf` reports "Permission denied" / "Directory not empty", `chmod -R u+w <dir>` first, then retry. How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mac Disk Cleanup
Help the user reclaim disk space on macOS safely. The golden rule: you find and show, the user decides. Never delete anything the user hasn't explicitly approved, and only ever surface things that are genuinely safe to remove (caches, rebuildable artifacts, duplicates, leftovers) — never their actual documents, code, photos, mail, or app data.
Core principles (read these first)
- Scan is read-only. Deletion is interactive. The scan never deletes. After showing findings, ask the user what they want removed, then delete only those.
- Only surface SAFE-to-delete items. Safe = regenerates automatically (caches), is rebuildable (node_modules, build output), is a duplicate, or is a leftover (old versions, updater installers, orphaned temp files). When something holds real data (databases, mail, project source, photos, volumes), either leave it out or clearly label it "🔴 real data — review only" and never delete it without an explicit, specific yes.
- Always show before deleting. Present findings grouped by size and safety. Let the user see exactly what would go and how much it frees.
- The user has the call. Use the AskUserQuestion tool to let them pick categories/folders. Default to the safest option. Never assume "delete everything."
- Ask when unsure. If a folder's purpose or structure isn't clear (e.g. an unfamiliar app, an ambiguous project layout, something that might be real data), ask the user what it is before treating it as deletable. It's always better to ask than to delete something that mattered.
- Verify, don't claim. After deleting, re-measure and report the actual space freed. Never report something as cleaned without confirming it's gone.
Workflow
Step 1: Run the scan
Run the bundled scanner — it's read-only and prints findings grouped by category with sizes:
bash <skill-path>/scripts/scan.sh
It accepts optional flags:
--deep— also scans~/Documents,~/Desktop,~/Developer, and other common project locations fornode_modulesand Python.venvdirectories (slower, but finds the biggest wins).--path <dir>— scan an additional custom directory for project artifacts.
What ships with it
2 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.
- 1mo ago First seen · 75 lines · 166 tokens per session scan D fcb71e818250
mac-disk-cleanup is a skill published in the GitHub repository Mateeb11/skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 166 tokens to every session and 1,523 once invoked, about $0.0007 per session on Opus 5.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-31.
Other skills, from other repositories
xcode-disk-cleanup
Audit and safely clean Xcode-related developer storage on macOS. Use whenever a developer mentions low disk space, Xcode storage, DerivedData, simulator devices or runtimes, stale beta platforms in Xcode Settings, DeviceSupport, archives, dSYMs, CocoaPods caches, simulator dyld caches, project .build folders…
anti-sleep
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
macos-disk-cleanup
A macOS disk-space diagnostic and cleanup workflow, including hidden “System Data” storage. It examines developer files, package-manager caches, containers, virtual machines, browser profiles, and leftover app data.
free-space
Free up disk space on a Mac safely. Scans for reclaimable space — app caches, developer caches (npm/uv/cargo/gradle/…), local AI models (Ollama/HuggingFace), Trash, Xcode build data, Docker images, leftover data from uninstalled apps, old nodemodules, and large stray files — then deletes only what the user approves.…
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…