Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops/plugin install opsWrote 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/lifecycle-innovations-limited/claude-ops/ops-mac)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-mac"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-mac.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.1 | $0.00030 | $0.02035 |
| Opus 5 | $0.00015 | $0.01018 |
| Sonnet 5 | $0.00006 | $0.00407 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade B, and why
ops-mac scanned grade B with 1 finding 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 9d 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.
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --setglobalstate on How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS ► MAC — macOS Diagnose & Fix
Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).
One command for native macOS health: it bundles the macos-toolkit CLI suite, auto-installs it on first use, runs a read-only baseline, and remediates the common offenders behind explicit confirmations.
All work routes through ${CLAUDE_PLUGIN_ROOT}/bin/ops-mac, the single source of truth for install + probes + the aggregate audit. The bundled CLIs:
| Tool | Domain | ops-mac subcommand |
|---|---|---|
machealth |
composite health (CPU/mem/disk/thermal/battery/iCloud/TM/net) | health |
netwhiz |
network + WiFi diagnostics | net / net wifi |
macbroom |
disk cleanup & reclaimable cache scan | disk |
pstop |
process monitoring (CPU/mem hogs) | procs |
macdog |
security & privacy audit | security |
lanchr |
launchd agent/daemon health (doctor) |
launchd |
macctl |
power / display / audio control | power |
macfig |
hidden macOS defaults | defaults |
updater |
app update management | update |
Platform guard
This skill is macOS only. The dispatcher exits with code 3 on non-Darwin. For Linux/WSL/Windows system optimization use /ops:speedup (cross-platform). The two are complementary — /ops:mac is the deep macOS-native surface; /ops:speedup is the portable cleaner.
Two hard-won quirks (baked into the dispatcher)
machealth check/diagnosecan hang forever on a stuck Time Machine / iCloud probe (its checks run in parallel with no per-probe skip flag). Every machealth call is wrapped in a hardtimeout(default 25s, overrideOPS_MAC_MACHEALTH_TIMEOUT). If it trips, the other probes are still reliable — never block on it.- The toolkit's pretty TUI tables render EMPTY when stdout isn't a TTY. The dispatcher forces
--jsonfor headless/agent consumers (macbroom,pstop,macdog,lanchr). When you need machine data, always pass--json.
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.
- 9d ago First seen · 162 lines · 30 tokens per session scan B 119dce8f8f57
ops-mac is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 2,035 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
hotfix-triage
Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).