ワンクリックで
mole-mac-cleanup
Use when the user asks to clean, optimize, uninstall, inspect disk usage, or purge project artifacts on macOS.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when the user asks to clean, optimize, uninstall, inspect disk usage, or purge project artifacts on macOS.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when setting up or reviewing a development environment, especially Varlock env schemas, gitignored env files, macOS Keychain/local secret storage, SOPS/age optional GitOps secrets, CI secret access, dotenv bootstrapping, or secure local dev onboarding.
Use when the repo has .beans or the user mentions beans, beans-prime, flat-file issues, task tracking, or issue status changes.
Opinionated JB GitHub Actions release-attempt workflow. Use only when the repo already has .github/workflows/jb-release-v1.yaml (or equivalent JB release-attempt workflow) or the user explicitly asks to set it up. Do not use for ordinary local releases; use jb-local-release instead.
Use when the user asks to run a local release flow: prepare version/changelog changes, run local checks, commit, tag, and optionally publish only when explicitly requested.
Query MDN Web Docs through the official MDN MCP server using a persistent mcporter config, avoiding a direct MCP connection in the agent harness. Use when checking current web platform docs, CSS/HTML/JavaScript/Web API behavior, MDN browser compatibility data, Baseline support, or when the user asks whether a browser feature is supported.
Use when the user asks for Chrome MCP/DevTools MCP via mcporter, existing Chrome tabs, console/network inspection, screenshots, or performance traces.
| name | mole-mac-cleanup |
| description | Use when the user asks to clean, optimize, uninstall, inspect disk usage, or purge project artifacts on macOS. |
| author | Benjamin Jesuiter <bjesuiter@gmail.com> |
| metadata | {"clawdbot":{"emoji":"🧹","os":["darwin"],"requires":{"bins":["mo"]},"install":[{"id":"brew","kind":"brew","formula":"mole","bins":["mo"],"label":"Install Mole via Homebrew"}]}} |
Repo: https://github.com/tw93/Mole
Command: mo (not mole!)
Install: brew install mole
Note for humans:
mowithout params opens an interactive TUI mode. Not useful for agents, but you might wanna try it manually! 😉
All-in-one toolkit combining CleanMyMac, AppCleaner, DaisyDisk, and iStat Menus:
node_modules, target, build, etc.mo clean --dry-run # Preview cleanup plan
mo clean --dry-run --debug # Detailed preview with risk levels & file info
mo optimize --dry-run # Preview optimization actions
mo optimize --dry-run --debug # Detailed optimization preview
mo clean # Run deep cleanup (caches, logs, browser data, trash)
mo clean --debug # Cleanup with detailed logs
mo optimize # Rebuild caches, reset services, refresh Finder/Dock
mo optimize --debug # With detailed operation logs
What mo optimize does:
mo clean --whitelist # Manage protected cache paths
mo optimize --whitelist # Manage protected optimization rules
mo purge # Clean old build artifacts (node_modules, target, venv, etc.)
mo purge --paths # Configure which directories to scan
Config file: ~/.config/mole/purge_paths
mo installer # Find/remove .dmg, .pkg, .zip installers
Scans: Downloads, Desktop, Homebrew caches, iCloud, Mail attachments
mo touchid # Configure Touch ID for sudo
mo completion # Set up shell tab completion
mo update # Update Mole itself
mo remove # Uninstall Mole from system
mo --version # Show installed version
mo --help # Show help
Check what would be cleaned:
mo clean --dry-run --debug
If looks good, run cleanup:
mo clean
Optimize system (after cleanup):
mo optimize --dry-run
mo optimize
Clean dev project artifacts:
mo purge
mo clean)--dry-run first. Built with strict protections.--debug for detailed logs.