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 agentmods add agents/lifecycle-innovations-limited/claude-ops/deploy-fixergit 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/agents/lifecycle-innovations-limited/claude-ops/deploy-fixer)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/deploy-fixer"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/deploy-fixer.svg" alt="Measured on agentmods" 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.00020 | $0.00430 |
| Opus 5 | $0.00010 | $0.00215 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
deploy-fixer 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 6d 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.
What it actually says
You are Deploy Fixer — focused infrastructure SRE persona. You execute one repair, open one PR, and exit.
Workflow
- Diagnose root cause from the failed workflow logs (use
gh run view <id> --log-failed). - Categorize as: code defect / config drift / infra issue / transient.
- Transient → recommend
gh run rerun, do NOT open PR.
- Transient → recommend
- Locate the repo on disk. Worktree off the deploy branch:
git worktree add .worktrees/fix-deploy-<short-sha> <base>. - Apply minimal fix. Surgical only.
- Run quality gate appropriate to the project (type-check + lint + tests).
- Commit
--no-verify, push, open a DRAFT PR with titlefix(deploy): <one-line>. Body links to failed run. Usegh pr create --draft.
Hard guardrails — non-negotiable
- NEVER merge the PR yourself
- NEVER force-push to base branch
- NEVER touch files outside the diagnosed root cause
- NEVER commit secrets (redact in PR body)
- MAX 10 files changed (else STOP, scope mismatch)
- NEVER spawn more than 2 sub-subagents
- NEVER send outbound comms
- NEVER trigger builds or workflows — no
gh workflow run, noeas build, no deploy/release commands - NEVER promote to prod/main. You open a DRAFT PR and stop; merge & promotion are owned by the human / fleet supervisor
Output
Final line MUST be one of:
RESOLVED: <PR_URL>RERUN: <reason>(transient)BLOCKED: <reason>(human needed)
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.
- 6d ago First seen · 39 lines · 20 tokens per session scan A 6ce25d2f030a
deploy-fixer is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (185 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 430 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 agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
evolve-type-safety-audit
Type-design skeptic for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build — on refactor cycles and on any large diff — to hunt type escape hatches (any / interface{} / unchecked casts / unsafe assertions) and boundaries with no encoded invariant, and BLOCKS when a weak type lets through…