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 45ck/skill-harness --skill gh-actions-failure-triagegit clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/45ck/skill-harness/gh-actions-failure-triage)<a href="https://agentmods.dev/skills/45ck/skill-harness/gh-actions-failure-triage"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/gh-actions-failure-triage/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/45ck/skill-harness/gh-actions-failure-triage"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/gh-actions-failure-triage.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.00032 | $0.00208 |
| Opus 5.5 | $0.00013 | $0.00083 |
| Sonnet 5.5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
gh-actions-failure-triage 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.
What it actually says
Use this skill when CI is failing in GitHub Actions and the user wants the failure understood or fixed.
Process:
- identify the failing workflow, job, and step rather than saying only that CI is red
- pull the smallest useful failure snippet and the command or assertion that failed
- separate infrastructure noise from an actual code or test regression
- map the failure to the local file or behavior most likely responsible
- define the cheapest local verification before rerunning CI
Deliver:
- failing workflow and job
- short failure summary
- likely root-cause area
- proposed fix path
- exact verification steps to run locally first
Avoid:
- dumping huge logs without synthesis
- treating every failure as a code defect when the runner or external service is the real problem
- changing unrelated code just to make the pipeline go green
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 · 29 lines · 32 tokens per session scan A 932f346aa559
gh-actions-failure-triage is a skill published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 208 once invoked, about $0.0001 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
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
troubleshooting
Debug a specific failure, investigate an incident, analyze error logs, or diagnose connectivity on the project's platform. NOT for proactive instrumentation (use monitoring/observability) or writing tests (use testing).
do-it-audit
Use when the user explicitly requests a deep repository or scoped audit; not for ordinary diff review.
do-it-code-quality
Use when designing, changing, or debugging code to locate causal ownership and close the affected behavior.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
github-ci-failure-triage
Use when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code.