Borrowing it
Nothing to install: this file belongs to berntpopp/gencc-link. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/berntpopp/gencc-link/main/.claude/skills/ci-failure-triage/SKILL.mdgit clone --depth 1 https://github.com/berntpopp/gencc-linkWrote 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/berntpopp/gencc-link/ci-failure-triage)<a href="https://agentmods.dev/skills/berntpopp/gencc-link/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/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/berntpopp/gencc-link/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/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.00039 | $0.00542 |
| Opus 5 | $0.00019 | $0.00271 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
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 9d 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
Classify the failure
Look at the GitHub Actions log and decide which stage failed. make ci-local
runs format-check, lint-ci, lint-loc, typecheck-fast, and test-fast;
the CI job then runs test-cov.
- Format check (
make format-check) — Ruff disagrees with the committed formatting. - Lint (
make lint-ci) — a Ruff lint rule. - File-size budget (
make lint-loc) —scripts/check_file_size.pyflags a file over the per-file line budget (see AGENTS.md "File Size Discipline"). - Typecheck (
make typecheck-fast) — mypy strict. - Tests (
make test-fast) — a failing or erroring test. - Coverage (
make test-cov) — coverage fell below the 85% gate. - Release (
release.yml) —make ci-local, the Compose config validation, or the Docker image build failed.
Reproduce locally
Run the same Make target that failed:
make format-check
make lint-ci
make lint-loc
make typecheck-fast
make test-fast
make test-cov
# release-only:
docker compose -f docker/docker-compose.yml -f docker/docker-compose.prod.yml config
docker build -f docker/Dockerfile -t gencc-link:ci .
Tests that need the live GenCC download are marked integration and are excluded
from test-fast / test-cov. Most unit tests build SQLite from the
tests/fixtures/ sample TSV and do not hit the network.
Fix at root cause
- Do not add
# type: ignoreor# noqato silence a check unless the behavior is genuinely correct and the tool is wrong. - Do not use
git commit --no-verifyto bypass pre-commit. - If
lint-locfails, split the oversized file rather than raising the budget. - For a flaky test, rerun once to confirm flakiness, then mark it
slow(orintegrationif it needs the network) and open a follow-up issue rather than disabling it.
Confirm fix
Run make ci-local locally. Push. Watch the workflow re-run.
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.
- 9d ago First seen · 58 lines · 39 tokens per session scan A 3fe94de27383
ci-failure-triage is a skill published in the GitHub repository berntpopp/gencc-link (0 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 542 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
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
report-issue-framework
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.
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.
temps-plugin
Build external plugins for the Temps deployment platform. Use when the user wants to create, modify, or debug a Temps plugin binary — a standalone Rust process that communicates with Temps over a Unix domain socket. Also use when the user mentions "temps plugin", "external plugin", "plugin binary", "plugin for temps"…