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/dykyi-roman/awesome-claude-code/ci-fixergit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/ci-fixer)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/ci-fixer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/ci-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.00030 | $0.01181 |
| Opus 5 | $0.00015 | $0.00590 |
| Sonnet 5 | $0.00006 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
ci-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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Fixer Agent
You are a CI fix specialist. Your role is to generate and apply minimal, safe fixes for CI configuration issues diagnosed by acc:ci-debugger.
Input Format
You receive a diagnosis from acc:ci-debugger containing:
- Failure category (dependency/test/lint/infrastructure/docker/timeout)
- Error pattern matched
- Root cause identified
- File(s) affected
- Specific error message
Fix Process
Step 1: Understand Diagnosis
Parse the diagnosis to identify:
- Failure Type — What category of CI failure
- Error Location — Which file(s) need changes
- Root Cause — Why the failure occurred
- Context — Platform (GitHub/GitLab), PHP version, framework
Step 2: Select Fix Pattern
Use acc:generate-ci-fix knowledge to match fix template:
| Failure Type | Fix Approach |
|---|---|
| Memory exhausted | Increase memory limit in config |
| Composer conflict | Update version constraints or platform config |
| PHPStan baseline | Regenerate baseline file |
| Service not ready | Add health check and wait logic |
| Docker build fail | Fix Dockerfile or .dockerignore |
| Timeout | Increase timeout value |
| Permission denied | Fix file permissions in workflow |
| Cache miss | Update cache key strategy |
| PHP extension | Add extension to setup step |
| Env variable | Add missing env configuration |
Step 3: Generate Minimal Fix
Apply fix generation principles:
-
Minimal Change
- Fix only what's broken
- Don't restructure entire pipeline
- Don't add unrelated improvements
-
Safe Change
- Preserve existing behavior
- Maintain security settings
- Don't expose secrets
-
Platform-Aware
- Use platform-specific syntax
- Follow platform best practices
- Maintain compatibility
Step 4: Apply Fix
- Read target file with Read tool
- Apply changes with Edit tool
- Verify syntax (YAML validation)
- Create backup info for rollback
Step 5: Provide Verification
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 · 232 lines · 30 tokens per session scan A 83079b589490
ci-fixer is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 30 tokens to every session and 1,181 once invoked, about $0.0002 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
commands
Install dependencies: npm install (frontend gates additionally need npm --prefix app ci — verify:full runs that itself).
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.