Borrowing it
Nothing to install: this file belongs to incubateur-ademe/benefriches. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/incubateur-ademe/benefriches/main/.agents/skills/fix-ci/SKILL.mdgit clone --depth 1 https://github.com/incubateur-ademe/benefrichesWrote 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/incubateur-ademe/benefriches/fix-ci)<a href="https://agentmods.dev/skills/incubateur-ademe/benefriches/fix-ci"><img src="https://agentmods.dev/badge/skills/incubateur-ademe/benefriches/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/skills/incubateur-ademe/benefriches/fix-ci"><img src="https://agentmods.dev/badge/skills/incubateur-ademe/benefriches/fix-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.01798 |
| Opus 5.5 | $0.00038 | $0.00719 |
| Sonnet 5.5 | $0.00019 | $0.00360 |
| Haiku 4.5 | $0.00009 | $0.00180 |
Grade A, and why
fix-ci 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 24d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix CI — diagnose and fix a failed GitHub Actions job run
Take a failed GitHub Actions run, deterministically identify what failed, reproduce it in an isolated worktree based on the exact failing commit, fix it, and verify green locally. Integration (commit/push/merge) is left to the user.
Determinism rule (non-negotiable)
All GitHub access goes through the fixed gh CLI commands documented below, with the
flags shown. Do not use the browser MCP, do not hand-craft REST calls, and do
not improvise alternative gh invocations. This keeps data-gathering reproducible.
Prerequisite: gh auth status must succeed. If not, stop and tell the user to run
gh auth login.
Procedure
1. Resolve the run
- If the user passed an argument, extract the run ID (and job ID if present):
- From a URL like
https://github.com/<owner>/<repo>/actions/runs/<id>→ take<id>. - From
.../runs/<id>/job/<jobId>→ take<id>and<jobId>. A job URL names the exact job the user cares about, so carry<jobId>into step 2 to skip job selection. - From a bare number → use it directly.
- From a URL like
- If no argument, pick the latest failed run on the current branch:
Take the first result. If none, report "no failed run found for this branch" and stop.gh run list --branch "$(git branch --show-current)" --status failure --limit 1 \ --json databaseId,headSha,headBranch,workflowName - Fetch run metadata (single deterministic call):
gh run view <id> --json databaseId,workflowName,headBranch,headSha,conclusion,jobs
2. Select the failed job
- If a
<jobId>came from a job URL (step 1), use that job. - Otherwise, from
.jobskeep those withconclusion == "failure"and take the first one — picking deterministically (rather than asking) keeps the skill non-interactive. If more than one job failed, note in your final report that the others exist so the user can re-run/fix-cifor them. - Record the selected job's numeric id (
.jobs[].databaseId) as<jobId>— step 3 uses it to scope the logs. - Classify — bail early on deploy/infra: if the job name matches deploy / scalingo / production / staging, this is not a code fix. Print a diagnosis from the logs (step 3) and stop — do not create a worktree or edit anything.
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.
- 24d ago Changed b5c82d13e7ae
- 2mo ago First seen · 154 lines · 94 tokens per session scan A 2156cfea70b5
fix-ci is a skill published in the GitHub repository incubateur-ademe/benefriches (45 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,798 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.