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-inbox)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-inbox"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-inbox/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-inbox"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-inbox.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.00028 | $0.05973 |
| Opus 5 | $0.00014 | $0.02986 |
| Sonnet 5 | $0.00006 | $0.01195 |
| Haiku 4.5 | $0.00003 | $0.00597 |
Grade A, and why
ops-inbox scanned grade A 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# token_env is NOT bound to the MCP are scanned via direct curl from Bash How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS ► INBOX ZERO
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).
⚠️ WHATSAPP TRANSPORT — MCP ONLY, NEVER wacli
For all WhatsApp operations in this skill (list chats, read messages, search contacts, send replies, archive chats), use the mcp__whatsapp__* tool family backed by the whatsmeow (Go) whatsapp-bridge — upstream lharries/whatsapp-mcp. (Earlier docs misnamed this as "Baileys" — Baileys is the Node.js WhatsApp library; this bridge uses go.mau.fi/whatsmeow.)
Server name.
mcp__whatsapp__*is the single-account default. Installs with more than one account register one server per account (whatsapp-nl,whatsapp-us,whatsapp-personal,whatsapp-work, ...) and have no plainmcp__whatsapp__*at all.whatsapp-cosis not an account — do not send on it. Resolve the real name from the available tools before the first call, and when several accounts exist, scan each one separately and keep the results labelled by account. See CLAUDE.md / ops-rules Rule 8.
NEVER call the legacy wacli CLI (wacli chats list, wacli messages list, wacli send, wacli doctor, wacli history backfill, etc). The wacli store and keepalive daemon are deprecated for this skill.
If you find yourself reaching for any wacli ... shell command, stop and use the MCP tool with the same intent:
| Intent | ✅ Use this | ❌ Do NOT use |
|---|---|---|
| List recent chats | mcp__whatsapp__list_chats {sort_by: "last_active", limit: 25} |
wacli chats list |
| Read full thread | mcp__whatsapp__list_messages {chat_jid, limit: 20} |
wacli messages list |
| Full-text search | mcp__whatsapp__list_messages {query: "<text>", limit: 20} |
wacli messages search |
| Resolve a contact | mcp__whatsapp__search_contacts {query: "<name>"} |
wacli contacts |
| Send a reply (after approval) | mcp__whatsapp__send_message {recipient: "<JID>", message: "<text>"} |
wacli send |
| Health check | ops-wa-accounts --list, then curl -s -o /dev/null -w "%{http_code}" "$WA_API/api/v1/status" (401 is healthy when the route is Bearer-gated). Never lsof :8080, never launchctl kickstart unless policy says the bridge is local. |
wacli doctor / ~/.wacli/.health |
| Trigger history backfill | curl -fsS -X POST "$WA_API/api/backfill" (resolve $WA_API first — see "WHICH NUMBER" below; claude-ops patch — runs per-chat against the 50 most-recent chats; bridge also auto-backfills 5s after every Connected event) |
— |
What ships with it
5 files 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.
- 3d ago Changed · +48 lines 40d68794d066
- 10d ago First seen · 307 lines · 28 tokens per session scan A 06fe3c64ac20
ops-inbox is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 5,973 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
meeting-agenda-optimizer
Designs effective meeting agendas, reduces meeting waste, and creates structured formats for recurring meetings. Analyzes meeting patterns to recommend which meetings to keep, combine, or eliminate.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.