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-deploy-fix)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-deploy-fix"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-deploy-fix/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-deploy-fix"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-deploy-fix.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.00032 | $0.02984 |
| Opus 5 | $0.00016 | $0.01492 |
| Sonnet 5 | $0.00006 | $0.00597 |
| Haiku 4.5 | $0.00003 | $0.00298 |
Grade A, and why
ops-deploy-fix 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use `run_in_background: true` (Rule 4) for any CLI install / brew / curl / `tmux source-file` triggered along the way. How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ops:deploy-fix — Auto-fix subsystem control surface
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).
This skill is the operator console for the post-merge + build-failure auto-fix loop installed by /ops:setup Step 6.5a. The underlying daemons, hooks, and prompts live in ${CLAUDE_PLUGIN_ROOT}/scripts/, ${CLAUDE_PLUGIN_ROOT}/hooks/, and ${CLAUDE_PLUGIN_ROOT}/prompts/. State lives in ~/.claude/state/ops-deploy-fix/. Logs live in ~/.claude/logs/ops-deploy-fix/.
Plugin rules apply (see claude-ops/CLAUDE.md). In particular:
- Rule 0 — never echo personal data (slugs are fine, but redact tokens, webhooks, emails)
- Rule 1 — max 4 options per
AskUserQuestion - Rule 4 — background by default during
configure - Rule 5 — destructive ops (clearing locks, wiping state) require explicit per-action confirmation
- Rule 6 — this skill never sends outbound comms; if a future flow needs to, use the universal send gate
Arguments
The first positional argument selects the subcommand. If absent, present:
/ops:deploy-fix — what do you want to do?
[status]
[tail]
[configure]
[test]
Subcommands:
| Subcommand | Purpose |
|---|---|
status |
Dashboard of recent monitor runs, fixer dispatches, locks, budget |
tail |
Follow the latest fixer log live |
configure |
Re-run the wizard from /ops:setup Step 6.5a |
test |
Send a synthetic failure through the pipeline (dry-run, no real fix) |
Subcommand: status
Print a compact dashboard. Read all data via Bash; favor parallel reads.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OPS ► DEPLOY-FIX STATUS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Master switch: <on|off> (deploy_fix_enabled)
Auto-dispatch: <on|off> (auto_dispatch_fixer)
Danger flag: <on|off> (allow_dangerous)
Budget cap: <N>/hour/repo (max_fixes_per_hour)
Notify channel: <macos|ntfy|discord|none>
Fix model: <haiku|sonnet|opus>
Last 5 monitor runs:
2026-04-26T08:14Z owner/repo-a:dev merge-watch deploy-success
2026-04-26T08:11Z owner/repo-b:main build-watch transient → rerun
...
Last 5 fixer dispatches:
2026-04-26T08:09Z owner/repo-b:main build-fix.md in-flight pid 41123
2026-04-26T07:42Z owner/repo-a:dev deploy-fix.md done log:fix-...log
Active locks:
owner/repo-b:main:build pid=41123 (alive)
Hourly budget remaining (this hour, <YYYYMMDD-HH>):
owner/repo-a 2 / 3
owner/repo-b 1 / 3
──────────────────────────────────────────────────────
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 · 260 lines · 32 tokens per session scan A 4c1e9530cc36
ops-deploy-fix is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,984 once invoked, about $0.0002 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
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
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).
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
bun-sveltekit
Use when building or running SvelteKit apps on Bun, including SSR, adapters, and Bun-specific APIs.
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…