Mole CLI
Mole inspects Mac storage and system state, cleans caches and build files, and previews selected items before deletion.
- 74,030 ★ on the repository
- Last commit
- GPL-3.0
Extended access
Why this level
- Cleanup can permanently delete caches, logs and build files; maintenance can change system state.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/moleDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Cleanup can permanently delete caches, logs and build files; maintenance can change system state.
This is third-party code. Review the repository files before installing.
What it does
Builds and removed applications can leave caches and related files on a Mac. In `mo`, users choose disk analysis or a specific cleanup operation. Mole groups build artifacts by project and leaves recently active files unselected. The official skill starts Claude Code, Codex and Cursor with a preview, leaving app removal and administrator steps to the user. By default, `mo uninstall`, `mo analyze` and `mo slim` send selected files to Trash after confirmation. Cache and build cleanup can delete files permanently.
Who it is for. Mac owners with large projects and caches investigating disk usage before cleanup.
Good fit when
- Storage is full and large directories are hard to locate.
- Completed projects have left rebuildable artifacts behind.
- A removed application has left caches and supporting files.
- A slow Mac needs inspection of CPU, memory and disk activity.
Not a fit when
- Files would be deleted without reviewing a preview.
- Every cleanup must be recoverable from Trash.
- The OS does not match the selected Mole branch requirements.
Example request
Show disk analysis and a dry-run for old Mac build artifacts without deleting anything.Limitations
The main branch requires macOS 12 or later, with other operating systems handled separately. clean, purge and installer delete permanently, so preserve needed items and inspect dry-run first. Some system operations need administrator access, but do not run the entire tool with sudo. If Mole cannot read the protected-path list, clean, purge and optimize stop rather than proceeding without exclusions.
How to disable. Quit Mole. Use documented `mo remove` to uninstall; this does not restore previously cleaned files.
FAQ
What is the command?
`mo`. Start with its menu or `mo --help`.
Can I preview cleanup?
Yes. `--dry-run` lists affected paths without deleting them, with details for the selected operation.
Where is history?
Use `mo history`, or `mo history --json` for processing.
Does Homebrew install the Mac app?
No, only the CLI. The native app is distributed separately.
How do I protect a cache?
Add the cache with `mo clean --whitelist`. Saved selections apply to later cleanups.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI locates large dependency directories for selected removal, with JSON output an agent can use to plan cleanup.
Simplify Codebase
simplify-codebase
A skill that says prove first and delete after: finding accidental complexity in code and safe removal without breakage. The README is in Chinese
Clifm is a file manager that opens a batch of filenames in an editor and asks for confirmation before renaming them.
broot is a terminal file manager that calculates directory sizes in the background to show large folders before cleanup.
Eleven skills for Claude Code and Codex: test audit, git worktree cleanup, plan pages, screen recording transcripts and 1Password sign-in
app-it builds a macOS app from a local web project, with its own Dock icon and window and a clean stop of the dev server on quit
README in short
After app removal, Mole lists references in shell, hook and MCP configuration by file and line without editing those settings.