An operations guide that recommends the next action for ongoing projects. It checks saved preferences, service health, active work notes, and, when configured, home-automation alarms.

Use it when deciding the next task, setting priorities, or checking whether project or home-system issues need attention.

It helps turn scattered project status information into a priority list of what to do next.

ops-next — Skill for Claude Code by Lifecycle-Innovations-Limited

Install

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.

Claude Code

/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops

Claude Code

/plugin install ops

Made for: Claude Code.

Or install ops, the plugin that ships this one along with the rest of its 66 skills, 21 agents, 5 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-next/github.svg)](https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-next)

Your own site

<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-next"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-next/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-next"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,898 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.01898
Opus 5	$0.00014	$0.00949
Sonnet 5	$0.00005	$0.00380
Haiku 4.5	$0.00003	$0.00190

Measured 9d ago against content hash cef854263e6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

ops-next 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. **Preferences**: `cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` — read `owner`, `primary_project`, `default_channels`

claude-ops/skills/ops-next/SKILL.md · 217 lines

How it starts

The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Runtime Context

Before advising, load:

Preferences: cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json — read owner, primary_project, default_channels
Daemon health: cat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json — flag any action_needed as priority
Ops memories: Check ${CLAUDE_PLUGIN_DATA_DIR}/memories/topics_active.md for ongoing work context
Home automation: If home_automation is configured in $PREFS_PATH, probe Homey via /ops:ops-home status for active alarms before composing the priority stack.

OPS ► NEXT ACTION

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).

CLI/API Reference

gh CLI (GitHub)

Command	Usage	Output
`gh pr list --state open --json number,title,statusCheckRollup,reviewDecision`	Open PRs with CI/review status	JSON array

Agent Teams support

If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when gathering priority data in parallel. This enables:

Agents share context and can coordinate mid-flight
You can steer priorities in real-time
Agents report progress as they complete

Team setup (only when flag is enabled):

TeamCreate("next-team")
Agent(team_name="next-team", name="fires-checker", prompt="Check infra health and CI for production fires")
Agent(team_name="next-team", name="comms-checker", prompt="Check unread messages across all channels")
Agent(team_name="next-team", name="prs-checker", prompt="Find PRs ready to merge — CI green, reviews approved")
Agent(team_name="next-team", name="sprint-checker", prompt="Check Linear sprint for highest-priority in-progress issues")

Read the full file on GitHub · 217 lines

Changes

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 · 217 lines · 27 tokens per session scan B cef854263e6b

Subscribe to this mod's changes

ops-next is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,898 once invoked, about $0.0001 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.

Claude Code DevOps and cloud Planning Productivity ai-agent ai-automation business-operations claude-code-plugin

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.

Adri3l-R3nan/cognify-skills · 41 tokens

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.

kenryu42/cc-safety-net · 65 tokens

ops-next