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 yeaight7/agent-powerups --skill github-ci-failure-triagegit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/github-ci-failure-triage)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/github-ci-failure-triage"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/github-ci-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/yeaight7/agent-powerups/github-ci-failure-triage"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/github-ci-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.00030 | $0.00769 |
| Opus 5.5 | $0.00012 | $0.00308 |
| Sonnet 5.5 | $0.00006 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
github-ci-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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce a clean, GitHub-native readout of failing PR checks before any code is edited. Triage first: summarize the breakage and propose a local fix plan; implement only after approval when the task is framed as triage-first.
When to Use
- A PR is red and the cause is unknown
- The user asks why CI is failing before asking for a fix
- A triage-first readout must precede any code edits
Inputs
- The PR number or URL (or the current branch to resolve it from)
ghCLI authenticated for the repository, or a GitHub connector
Core Rules
- Resolve the PR first
- Inspect failing checks before guessing
- Prefer GitHub-native data (
ghor a GitHub connector) over screenshots or copied snippets - Summarize the failure before proposing code changes
- Implement only after approval when the task is framed as triage-first
- Do not auto-commit, auto-push, or auto-rerun remote writes without approval
Workflow
-
Resolve the PR:
gh pr view <number-or-url> --json number,title,headRefName,url gh pr view --json number,title,headRefName,url # from the current branch -
Inspect failing checks. List checks, isolate failing GitHub Actions jobs, and pull only the failing logs:
gh pr checks <number> gh run list --branch <head-branch> --limit 10 gh run view <run-id> --json jobs # job-level status gh run view <run-id> --log-failed # logs from failing steps onlyIf a check is external (not GitHub Actions), report its URL and keep it out of local log parsing.
-
Summarize the failure:
- failing job
- likely root cause
- relevant log snippet
- affected files or subsystem
-
Propose the fix plan:
- what to change locally
- what to validate locally first
- what remains remote-only
-
Implement only when the user wants the fix. Keep changes traceable to the failing signal; rerun the narrowest meaningful local validation first.
Bundled Helper
scripts/inspect_pr_checks.py— use it when you want a structured check summary instead of rawghoutput.
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.
- 1mo ago First seen · 87 lines · 30 tokens per session scan A 1131e16b5864
github-ci-failure-triage is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 16d ago), licensed Apache-2.0. It adds 30 tokens to every session and 769 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-09-14.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
simplify-code
Sequential 3-lens cleanup of recent code changes.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
hqe
Comprehensive codebase health auditing, remediation, and verification skill based on the canonical HQE Protocol v5.0.0.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.