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 Starfie1d1272/dsh-github-skills --skill gh-fix-cigit clone --depth 1 https://github.com/Starfie1d1272/dsh-github-skillsWrote 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/starfie1d1272/dsh-github-skills/gh-fix-ci)<a href="https://agentmods.dev/skills/starfie1d1272/dsh-github-skills/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/starfie1d1272/dsh-github-skills/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/starfie1d1272/dsh-github-skills/gh-fix-ci"><img src="https://agentmods.dev/badge/skills/starfie1d1272/dsh-github-skills/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.00043 | $0.00424 |
| Opus 5 | $0.00022 | $0.00212 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00042 |
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 10d 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.
What it actually says
GitHub Actions CI Fix
Diagnose or fix failing GitHub Actions checks on a pull request, from real check and log evidence. "Current branch" resolves to its associated PR; branch-only Actions runs without a PR are outside this workflow.
Evidence
- Establish the root cause only from real check state, logs, and diff evidence; never fabricate a failure reason from a single error string.
- Use a visible capability for PR metadata and checks when it is
semantically sufficient; use a capability that exposes actual logs when
available; otherwise use
scripts/inspect-pr-checks.mjsorgh. - Non-Actions CI is report-only: check name + URL + state, never their logs.
- Missing, pending, or inconclusive logs are uncertainty — report them as such, do not guess.
Workflow
- Resolve the PR (given number/URL, or current branch via local git context; ask if still ambiguous).
- Gather failing-check evidence (see Evidence) and summarize failures with run URLs and log snippets.
- Diagnose-only requests get a root cause and explanation only.
- Fix mode (only when the user asked to fix): apply the minimal local change tied directly to the root cause, run the most relevant local verification, then recheck the status. If the failure is clearly unrelated to the local diff, say so before proposing code changes.
- Report: evidence, root cause, changed files, verification run, and residual risk.
Remote write boundary
Local edits are allowed under "fix the CI" intent. Pushing, re-running a workflow, and commenting on the PR require explicit user request or the host approval boundary.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 43 lines · 43 tokens per session scan A 2717de201351
gh-fix-ci is a skill published in the GitHub repository Starfie1d1272/dsh-github-skills (6 stars, last pushed 22d ago), licensed Apache-2.0. It adds 43 tokens to every session and 424 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
github-ci-debug
Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.
agentdebug
Use AgentDebugX for trajectory diagnosis only when the user explicitly asks to use AgentDebug, AgentDebugX, or the agentdebug skill. Do not invoke for generic debugging, diagnosis, inspection, or trajectory-review requests.
agentdebug
Use AgentDebugX only when the user explicitly asks for AgentDebug, AgentDebugX, or the agentdebug skill. Do not invoke for generic debugging or trajectory review.
actions-debugging
Use when a GitHub Actions workflow fails — diagnose the run log, identify the root cause, and apply a targeted fix.
sentry-fix-verification
Verify a production fix by linking the changed code and release to Sentry issue state and post-release event trends without resolving issues prematurely.
sentry-issue-investigation
Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.