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 jakesterns/agent-skills --skill ci-failure-triagegit clone --depth 1 https://github.com/jakesterns/agent-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/jakesterns/agent-skills/ci-failure-triage)<a href="https://agentmods.dev/skills/jakesterns/agent-skills/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/jakesterns/agent-skills/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/jakesterns/agent-skills/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/jakesterns/agent-skills/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.00031 | $0.00265 |
| Opus 5 | $0.00015 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
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 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
CI Failure Triage
Use this skill when a CI or deployment job fails and the user provides logs, workflow files, or job metadata.
Inputs
- CI logs, failing job and step names, workflow YAML, recent commits, dependency changes, and environment details
Steps
- Locate the first failing step and first meaningful error.
- Classify the failure: test regression, build error, dependency resolution, cache issue, credentials/permissions, environment drift, rate limit, flaky test, or deployment failure.
- Compare the failing step to workflow configuration and recent changes.
- Identify whether retrying is reasonable or whether a code/config fix is required.
- Recommend the smallest fix and any workflow hardening that prevents recurrence.
- Provide commands or workflow rerun steps when appropriate.
Output
Return:
- Failure classification
- Root cause hypothesis with evidence
- Minimal fix plan
- Retry guidance
- Preventive hardening suggestions
Guidelines
- Do not focus on the last error if earlier setup failed.
- Be explicit when logs are insufficient.
- Separate likely root cause from secondary noise.
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 · 38 lines · 31 tokens per session scan A 5196c0b600cc
ci-failure-triage is a skill published in the GitHub repository jakesterns/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 265 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
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.