🐹 Clean, uninstall, analyze, optimize, and monitor your Mac from the terminal.
mo binary.| Rating | Summary | |
|---|---|---|
| Quality | solid (19/24) | Actively maintained with exemplary documentation; loses points only on engineering signals inherent to Shell — no typed language, no formal manifest, no visible test infrastructure. |
| PAI Relevance | integrate (0.63) | A subprocess-callable macOS maintenance CLI filling a clear gap — PAI has no system maintenance skill — constrained to the Mac host side of the stack. |
19/24 — actively-maintained / well-documented / early-or-minimal
Failed:
.github/workflows/ appears in the provided data.Passed:
archived: false.Failed:
Passed:
brew install mole) and curl-script install with optional version pinning documented.--dry-run, --debug, --whitelist, --nightly, --json across all subcommands.Failed:
Passed:
| Dimension | Score | Assessment |
|---|---|---|
| Harvest Value | 1 | The append-only ~/Library/Logs/mole/operations.log with mo history --json and the whitelist protection system are interesting patterns for auditable, reversible CLI operations — applicable to how PAI hooks log destructive actions — but not architecturally novel enough relative to PAI's existing hook infrastructure to score 2. |
| Integration Readiness | 1 | Shell binary callable via bun.spawnSync("mo", ["clean", "--dry-run"]) with clean exit codes and human-readable output; Homebrew-installable on Mac in one command. Cannot run on PAI's Linux VM — macOS-only — so integration is restricted to Mac-host subprocess contexts. |
| Overlap Risk | 0 | No PAI skill or hook covers Mac system maintenance, disk analysis, cache cleanup, or app uninstallation. StacksUp manages tool subscriptions but performs no filesystem cleanup or system monitoring. Confirmed clear gap. |
| Gap Fill | 1 | Addresses local Mac host maintenance — a functional area with zero PAI coverage. This is operational rather than intelligence-layer, so it does not constitute a core AI infrastructure gap (score 2), but it is a genuine functional void for a Mac-based PAI operator. |
Composite: 0.63
Capture-to-Knowledge pipeline maintenance: Install Mole with the one-liner from the README (curl …/install.sh | sh), then add mo clean as the opening step in your pipeline's shell wrapper — this clears accumulated temp JSON responses, LLM API caches, and browser-session artifacts before each ingestion run, keeping disk pressure predictable across multi-day batch sessions without manual intervention.
Fabric pattern evaluation runs (fab v2.1+): Launch mo monitor in a terminal split alongside any Fabric pattern eval that processes large content batches — the live CPU, RAM, and disk I/O readout surfaces bottlenecks in real time without leaving the terminal, replacing the need to alt-tab to Activity Monitor when a pattern pipeline stalls or a Bun process spikes unexpectedly.
Pre-download disk audit for pipeline experiments: Before pulling model weights, large corpora, or new Fabric pattern sets, run mo analyze from the home directory — it produces a ranked breakdown of actual space consumers (Xcode DerivedData, Docker image layers, bun/pnpm caches) rather than a raw du dump, giving a concrete list of reclaimable gigabytes before you commit to a large pull.
Category: Developer Tools & CLIs
In this category: casey--just (excellent, 21/24)
Standing: Mole (solid, 19/24) sits one tier below just in the same category but covers an entirely different problem — just targets developer task automation across any OS while Mole targets Mac system hygiene; they serve complementary, non-overlapping workflows.
Density: 9/10 — README (complete, ~8KB provided), star count, fork count, open issue count, creation date, last commit date, full release history, license, and topics all present. Dependency manifest not available (Shell project with no formal manifest convention). No CI configuration visible in provided data.
The star velocity (~6,600/month) for an 8-month-old Shell project is exceptional and indicates genuine product-market fit at scale. The companion commercial app (mole.fit — "One license covers 2 Macs, with lifetime updates") signals that the author treats this as a serious, long-term supported product rather than a side project, which is a strong maintenance durability indicator. The engineering score (4/8) reflects Shell's inherent lack of typed-language tooling and formal package management, not poor implementation discipline — the README's extensive safety documentation (SECURITY.md, SECURITY_AUDIT.md, whitelist system, dry-run modes, operation log) demonstrates careful engineering practice within the Shell idiom. The prior rolling-summary score of 4.6/24 ("poor") appears to have been an informal rough estimate; probe-based scoring yields 19/24 ("solid").