Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-deskgit clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-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-desk)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-desk"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-desk/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-desk"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-desk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 165 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.02912 |
| Opus 5 | $0.00014 | $0.01456 |
| Sonnet 5 | $0.00006 | $0.00582 |
| Haiku 4.5 | $0.00003 | $0.00291 |
Grade A, and why
ops-desk scanned grade A with 0 findings 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 11d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS ► DESK SWEEP
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).
Goal: everything sitting on the owner's desk — pending decisions, staged drafts awaiting approval, unpaid invoices to chase, documents to sign, blocked issues needing an owner action — becomes a ranked queue of ready-to-approve action packages, then gets worked down one item at a time. The success metric is the same spirit as inbox-zero: an empty desk, with every remaining item either executed, decided, or parked with an explicit reason and a reminder.
When to use ops-desk vs ops-inbox
/ops:ops-inbox— fresh inbound comms (who wrote me, what needs a reply)./ops:ops-desk— the standing backlog (what am I blocking, what decision is waiting on me, what draft is staged, what must I sign/pay/approve). Run it after an inbox pass, or whenever the owner says "what's left / get this off my desk".
Step 1 — Build the item list (unless passed explicitly in ``)
- Task tracker (SSOT). Whichever the box uses, in order of preference:
- Paperclip —
paperclip issue list -C <company-id>for each company in${CLAUDE_PLUGIN_DATA_DIR}/preferences.json → paperclip.companies[], falling back topaperclip company list. Keepstatus=blocked|todo|in_progressissues whose title/description implies an OWNER action — matcher:decision,owner decision,approve,sign,pay,chase,staged,awaiting owner,Rule-6. - Linear —
mcp__linear__list_issuesfiltered to the owner as assignee, when Paperclip is absent. - GitHub —
gh issue list --assignee @meas last resort.
- Paperclip —
- Inbox residue. Genuine NEEDS_REPLY plus todo/action-labeled emails surviving the
most recent
/ops:ops-inboxpass (runbin/ops-inbox-scanwithOIS_NO_REFRESH=1if one already ran this session). - Dedupe against items already handled this session, and collapse duplicate issues tracking the same underlying ask (mirror boards, Linear↔Paperclip twins).
- Shape each item as
{key, refs: [issue identifiers], hint}wherehintstates the concrete question to answer AND what must be verified (never trust the issue title alone).
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.
- 11d ago First seen · 215 lines · 28 tokens per session scan A 3541df7584f2
ops-desk is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 2,912 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
change-management-planner
Plans organizational change initiatives including technology rollouts, process redesigns, and team restructuring. Maps stakeholders, identifies resistance, designs communication plans, and builds adoption strategies with measurable milestones.
employee-onboarding-designer
Designs structured employee onboarding programs that reduce time-to-productivity and improve retention. Creates day-by-day onboarding plans, training checklists, milestone assessments, and 30/60/90 day success criteria tailored to the role type.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
work-unit-decomposition
Decompose implementation plans into discrete work units with enumerated DoD items, file scope declarations, dependency mapping, and human checkpoint flags.
anti-drift
Hierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.