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-mcp)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-mcp"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-mcp/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/lifecycle-innovations-limited/claude-ops/ops-mcp"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-mcp.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.00030 | $0.02693 |
| Opus 5 | $0.00015 | $0.01347 |
| Sonnet 5 | $0.00006 | $0.00539 |
| Haiku 4.5 | $0.00003 | $0.00269 |
Grade B, and why
ops-mcp 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat "$HOME/.claude/state/mcp-watchdog/state.json" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS ► MCP
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).
Surfaces the MCP auto-reconnect subsystem (watchdog + keepalive + reauth) as a discoverable slash command. These three scripts were previously orphaned — no plugin-level entry point. This skill is the entry point.
For full architecture reference (state files, scripts, failure modes) see STATUS.md.
Runtime Context
Before any route runs, resolve:
- State dir:
$HOME/.claude/state/mcp-watchdog— watchdog state, health, and logs. - Keepalive state dir:
$HOME/.claude/state/mcp-keepalive— keepalive logs and health. - Reauth state dir:
$HOME/.claude/state/mcp-reauth— reauth logs. - Plugin root:
${CLAUDE_PLUGIN_ROOT}— used to invoke scripts. - Claude config:
$HOME/.claude.json— source of truth for configured MCP servers.
If the watchdog state dir does not exist, the watchdog has never run — surface a setup hint on the status route.
Routing table
Parse $ARGUMENTS and route immediately. First token decides the route.
| First arg | Route |
|---|---|
(empty) / status |
Status dashboard — watchdog health + per-server states + last tick |
servers |
List all MCP servers from ~/.claude.json with current state |
reconnect [server] |
Manually trigger watchdog reconnect for one server or all |
reauth [server] |
Invoke ops-mcp-reauth.py for the named server (Playwright OAuth flow) |
logs [N] |
Tail N lines (default 50) of watchdog + keepalive logs |
restart |
Restart the watchdog (update crontab entry) |
test [server] |
Fire a no-op MCP probe against one server to verify reachability |
What ships with it
1 file 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.
- today Changed e9842384d8ee
- 10d ago First seen · 282 lines · 30 tokens per session scan B a13f35ada0c6
ops-mcp is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 2,693 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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).