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-releasegit 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-release)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-release"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-release/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-release"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.02245 |
| Opus 5.5 | $0.00010 | $0.00898 |
| Sonnet 5.5 | $0.00005 | $0.00449 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
ops-release 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS ► RELEASE — one-command plugin publish
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).
Cuts a new published version of the claude-ops plugin: bumps the version in the
three manifests, writes the CHANGELOG, opens a release PR, waits for CI, merges it to
main, and pushes the vX.Y.Z tag. After it runs, /ops:ops-update pulls the new
version down to the box.
ops-releaseships it ·/ops:ops-updatepulls it. Order: merge your fix PR →/ops:ops-release→/ops:ops-update.
⚠️ Run it from the REPO CHECKOUT, not the cache
bin/ops-release resolves its targets relative to its own location:
PLUGIN_DIR = <bin>/.., REPO_ROOT = <bin>/../.., and it needs
REPO_ROOT/.claude-plugin/marketplace.json. The plugin cache
(~/.claude/plugins/cache/ops-marketplace/ops/<ver>/bin/ops-release) has no
marketplace.json above it, so running the cache copy fails with
not found: …/.claude-plugin/marketplace.json. Always run the copy inside a
git checkout of the repo (the dir that has both .claude-plugin/marketplace.json
and claude-ops/bin/ops-release).
Resolve it first:
RELEASE=""
for d in ~/Developer/repos/claude-ops ~/Projects/claude-ops-workspace/claude-ops ~/Projects/claude-ops/claude-ops "$HOME"/Projects/*/claude-ops; do
if [ -f "$d/.claude-plugin/marketplace.json" ] && [ -x "$d/claude-ops/bin/ops-release" ]; then
RELEASE="$d/claude-ops/bin/ops-release"; REPO="$d"; break
fi
done
[ -n "$RELEASE" ] || { echo "no claude-ops checkout with marketplace.json found — clone the repo first"; exit 1; }
echo "using: $RELEASE (repo: $REPO)"
Make sure the checkout's main is up to date and includes the fix you want to
publish before releasing (git -C "$REPO" fetch origin && git -C "$REPO" checkout main && git -C "$REPO" pull --ff-only). The release branches from origin/main,
so anything not yet on origin/main will NOT be in the release.
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.
- 1mo ago Changed · +32 lines 26771e85d300
- 1mo ago First seen · 140 lines · 26 tokens per session scan A d97e385e2dc0
ops-release is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (545 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 2,245 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
update
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…
evolve-lite:publish
Publish a private entity (guideline, feedback, project or reference) to a configured write-scope repo.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.