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.5 | $0.00016 | $0.00303 |
| Sonnet 5.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 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.
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.
- 1mo 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 3mo ago), licensed MIT. It adds 39 tokens to every session and 758 once invoked, about $0.0002 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-31.
Other skills, from other repositories
jetbrains-dev
Use when building, running, or debugging the JetBrains plugin — Gradle build/typecheck tasks, sandbox runIde modes and recovery, stopping sandbox runs, dev storage isolation, debug/chat logging, CLI pin modes and pin bumping.
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
taste-lints
Use when you say run taste lints, check file size, or lint taste invariants. Custom lints with agent-readable remediation instructions for file size, naming conventions, structured logging, and complexity.
ai-agents-config-catalog
Catalog of every configuration axis in this repo, env vars, commit markers, frontmatter keys, QA skip verdicts, and escape hatches, each with its enforcement point and abuse story, plus the checklist for adding a new flag safely. Use when you say what does a skip flag do, list escape hatches, can I skip this gate, add…
ai-agents-debugging-playbook
Symptom-to-triage playbook for this repo's recurring failures. Blocked pushes, drift gate reds, plugin bump reds, coverage pin trips, hook exit 143, session NONCOMPLIANT. Maps each symptom to a first command, discriminating experiment, fix path, and trap. Use when you say triage this failure, why is my push blocked…