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 skills add euxx/claude-skills-for-copilot --skill gh-fix-cigit clone --depth 1 https://github.com/euxx/claude-skills-for-copilotWrote 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/euxx/claude-skills-for-copilot/gh-fix-ci)<a href="https://agentmods.dev/skills/euxx/claude-skills-for-copilot/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/gh-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/euxx/claude-skills-for-copilot/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/gh-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.00039 | $0.00758 |
| Opus 5 | $0.00019 | $0.00379 |
| Sonnet 5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
gh-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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Failing CI Checks
Use gh to locate failing PR checks, fetch GitHub Actions logs, summarize the failure, then propose a fix plan and implement only after explicit user approval.
Prerequisites
Verify gh authentication before doing anything else:
gh auth status
If unauthenticated, ask the user to run gh auth login (repo + workflow scopes required), then stop.
Workflow
1. Resolve the PR
# if the user specified a PR number or URL:
gh pr view <number-or-url> --json number,url,headRefName
# otherwise (current branch):
gh pr view --json number,url,headRefName
Extract owner and repo from the returned url field — PR URLs have the form https://github.com/<owner>/<repo>/pull/<number>, so split on / to get the 4th and 5th segments. These are the base (target) repository coordinates where GitHub Actions checks run, and are reliable even for cross-fork PRs.
2. Inspect failing checks
gh pr checks <pr-number> -R <owner>/<repo> --json name,state,bucket,link,startedAt,completedAt,workflow
If a field is rejected, rerun with the available fields reported by gh. Scope only to GitHub Actions checks. If link is not a GitHub Actions run URL, label it as external, report the URL only, and do not investigate further (e.g. Buildkite, CircleCI are out of scope).
3. Fetch failure logs
For each failing GitHub Actions check:
- Extract the run ID from
link(the numeric segment in the URL). - Fetch run metadata:
gh run view <run-id> -R <owner>/<repo> --json name,workflowName,conclusion,status,url,event,headBranch,headSha - Fetch logs:
gh run view <run-id> -R <owner>/<repo> --log - If the run is still in progress, get the job IDs and fetch logs directly:
Then for each relevant job:gh run view <run-id> -R <owner>/<repo> --json jobsgh api "/repos/<owner>/<repo>/actions/jobs/<job-id>/logs"
Extract a concise failure snippet (relevant error lines and stack traces only).
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.
- 11d ago First seen · 99 lines · 39 tokens per session scan A 9e29999b2e93
gh-fix-ci is a skill published in the GitHub repository euxx/claude-skills-for-copilot (4 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 758 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-31.
Other skills, from other repositories
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks". Always goes through npx mega-linter-runner (--install or --upgrade), then…
gh-fix-ci
Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose a plan, and only implement after explicit user approval. External CI providers (Buildkite, CircleCI, etc.) are reported by URL only.
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
megalinter
Entry point for everything MegaLinter. Use when the user wants to lint their repository, set up MegaLinter, check or fix lint errors, make CI lint jobs pass, or says "run megalinter", "fix lint errors", "make the linters happy", "clean up code quality". Detects the repository state and orchestrates the…
fix-ci
Diagnose and fix a failing CI run by pulling the actual failure logs (gh run view --log-failed), reproducing the failure locally, fixing the root cause rather than the symptom, and verifying green before and after pushing. Use when a GitHub Actions run is red, a PR check is failing, or CI passes locally but fails…
github-actions-silent-failures
Diagnose GitHub Actions workflows that fail silently — a reusable-workflow run that shows zero jobs and no logs (startupfailure), a gh-aw cross-repo import that mis-resolves when the source repo is literally named .github, and self-hosted-runner traps (a shared-tmp race across containers, docker exec landing as an…