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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/ops-ci-fix)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-ci-fix"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-ci-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/commands/christopherlouet/claude-base/ops-ci-fix"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-ci-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.00000 | $0.00326 |
| Opus 5.5 | $0.00000 | $0.00130 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
ops-ci-fix 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.
What it actually says
OPS-CI-FIX Agent
Diagnose and repair failing CI/CD pipelines.
Request context
$ARGUMENTS
Objective
Scan GitHub Actions workflows, identify failure causes, and apply automatic fixes when safe.
Use the ops-ci-fix skill for the detailed methodology.
Workflow
- Scan workflows and classify their state (failure, blocked, stale)
- Extract failure logs and diagnose the root cause
- Classify: test failure, build error, deps, auth, timeout, config
- Apply safe fixes (re-run, cancel stuck, fix YAML)
- Propose without applying risky fixes (source code, secrets)
- Verify the fixes (local tests + CI re-run)
- Generate a report with remaining manual actions
Expected output
- Diagnosis: table of workflows with identified cause
- Applied fixes: list of corrections made
- Manual actions: checklist for the user (secrets, runners)
- Recommendations: long-term improvements (cache, flaky tests)
Related agents
| Agent | Usage |
|---|---|
/ops:ops-ci |
Configure new CI pipelines |
/ops:ops-standup |
View the global state of the repos |
/dev:dev-debug |
Debug a specific test |
IMPORTANT: Always diagnose BEFORE fixing.
IMPORTANT: Never modify secrets — guide the user.
YOU MUST show the diff before modifying a workflow file.
NEVER force-push or modify git history.
Think hard about the root cause — a re-run is not a fix.
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 First seen · 51 lines · 0 tokens per session scan A b3f42cff7679
ops-ci-fix is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 326 tokens. 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 commands, from other repositories
deploy
Deploy application with pre/post-deploy checks.
recover-orphans
Scan for pipeline-orphaned issues stuck in intermediate workflow states and recover them — diagnose each orphan's actual GitHub state, apply recovery actions, clean up worktrees.
audit
Trace a production issue or pipeline failure end-to-end through GitHub artifacts, then file a detailed improvement issue to the Forge repo.
diagnose
Trace a failed or stalled pipeline run — identify which FORGE annotation is missing or malformed, diagnose the failure point, and suggest specific remediation steps.
compat-audit
On-demand Claude Code compatibility and feature parity report — compares installed version against the breakpoints registry and lists affected ForgeDock features.
incident-response
Coordinate P0 incident response — hotfix validation, timeline reconstruction, and post-incident analysis.