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/GabsFranke/claude-code-github-agentWrote 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/gabsfranke/claude-code-github-agent/fix-ci)<a href="https://agentmods.dev/commands/gabsfranke/claude-code-github-agent/fix-ci"><img src="https://agentmods.dev/badge/commands/gabsfranke/claude-code-github-agent/fix-ci/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/gabsfranke/claude-code-github-agent/fix-ci"><img src="https://agentmods.dev/badge/commands/gabsfranke/claude-code-github-agent/fix-ci.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.00009 | $0.07769 |
| Opus 5.5 | $0.00004 | $0.03108 |
| Sonnet 5.5 | $0.00002 | $0.01554 |
| Haiku 4.5 | $0.00001 | $0.00777 |
Grade C, and why
fix-ci scanned grade C with 2 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- **Never extract credentials** - Do not read git config or remote URLs to obtain tokens; MCP tools handle auth automatically Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- ❌ **NEVER use `curl`, `gh` CLI, or direct HTTP requests to fetch logs** - Always use MCP tools instead How it starts
The opening of the file, as written. The whole thing — 934 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Failure Analysis and Fix
Analyze GitHub Actions workflow failures and coordinate specialized agents to implement fixes. You orchestrate the entire process: create the branch, delegate work, and create the PR.
Arguments: "$ARGUMENTS"
- First argument: Repository (owner/repo format, required)
- Second argument: Workflow run ID or PR number (required)
IMPORTANT: A workflow run ID (e.g.,
24425975972) is NOT a commit SHA. It is a GitHub Actions run identifier — use it ONLY withmcp__github_actions__*tools (e.g.,get_workflow_run_summary). Never pass it tomcp__github__get_commitor any tool that expects a commit SHA. - Third argument: Failure type (optional: build, test, lint, deploy, all)
Context Variables Available:
Your prompt includes a ## Workflow Failure Context section with:
Run ID- The workflow run ID to analyzeHead Branch- The branch where the failure occurred (e.g.,feat/ci-fix)Target Branch for PR- Use this as thebasewhen creating your PRWorkflow Name,Failed Job,Conclusion- Additional failure metadata
CRITICAL: The Target Branch for PR field in your context tells you exactly which branch to target with your fix PR. This is the branch where the CI failure occurred. Always use it — never default to main or develop unless it explicitly says so.
Your Role as Orchestrator
You are the main coordinator with these responsibilities:
- Create a meaningful branch for the fix work
- Fetch workflow failure information from GitHub using MCP tools
- Analyze logs to identify failure type and scope
- DELEGATE to specialized agents (they implement ALL fixes)
- Create the PR with all fixes
- Post comprehensive results to GitHub
Key principles:
- YOU create the branch - Use meaningful names like
fix/ci-failure-run-{run_id} - YOU analyze and plan - Understand what failed and determine delegation strategy
- YOU NEVER implement fixes yourself - Always delegate to specialist agents
- Subagents implement ALL fixes - They work in your branch and commit their changes
- YOU create the PR - After all fixes are committed by agents
- YOU post the final summary - Comprehensive results to GitHub
ghCLI is NOT available - Never attemptghcommands; usemcp__github__*andmcp__github_actions__*tools exclusively
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 · 934 lines · 9 tokens per session scan C 355aa33a22f3
fix-ci is a command published in the GitHub repository GabsFranke/claude-code-github-agent (5 stars, last pushed 26d ago), licensed MIT. It adds 9 tokens to every session and 7,769 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (harvests environment variables, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.