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 ci-failure-readoutgit 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/ci-failure-readout)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/ci-failure-readout"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/ci-failure-readout/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/ci-failure-readout"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/ci-failure-readout.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.00028 | $0.00588 |
| Opus 5 | $0.00014 | $0.00294 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
ci-failure-readout 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 3d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
CI logs are notoriously noisy. Extract the one true error, prove it locally, and write a readout — do not dump the entire log into the context window.
When to Use
- A CI pipeline failed and the error is buried in long logs
- A readout is needed before deciding what (or who) fixes the failure
- A CI failure must be reproduced locally before fixing
Inputs
- Access to the CI run (e.g.,
ghfor GitHub Actions) or a downloaded log file - The repo, to rerun the failing command locally
Workflow
-
Locate the true error. Find the exact step that failed; ignore setup/teardown noise:
gh run list --limit 10 # find the failing run gh run view <run-id> # failing job and step gh run view <run-id> --log-failed # logs from failing steps only # or, with a downloaded log: grep -n -iE "error|failed|exit code" ci.log | head -20 -
Extract the trace. Copy only the stack trace or the specific compiler/linter error message — not the surrounding noise.
-
Reproduce locally. The first rule of fixing a CI failure is proving it fails locally. Run the exact command the CI runner used (read it from the workflow/step definition), e.g.:
npm run test:e2e # whatever the failing step actually ran -
Draft the readout. Before fixing it, write a 2-sentence summary: "CI failed during the
buildstep becausesrc/types.tsis missing an export." This forces you to understand the problem instead of blindly guessing.
Output
- The failing step, the extracted error (trace or message only), local repro status, and the 2-sentence readout
Verification
- Failing step identified by name, not "somewhere in CI"
- Only the relevant trace/error extracted — no full-log dumps in context
- Failure reproduced locally with the CI's exact command (or the gap explained)
- 2-sentence readout written before any fix
Failure Modes
- Log flooding — pasting thousands of lines into context instead of the failing step's error.
- Fixing without local repro — pushing speculative fixes and using CI as the test loop.
- First-red-line fallacy — the earliest red text may be a symptom; the failing step defines where to look.
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.
- 3d ago First seen · 59 lines · 28 tokens per session scan A d3af9ab557bf
ci-failure-readout is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 588 once invoked, about $0.0001 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-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.