Borrowing it
Nothing to install: this file belongs to berntpopp/uniprot-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/uniprot-link/main/.claude/skills/ci-failure-triage/SKILL.mdgit clone --depth 1 https://github.com/berntpopp/uniprot-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/uniprot-link/ci-failure-triage)<a href="https://agentmods.dev/skills/berntpopp/uniprot-link/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/uniprot-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/uniprot-link/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/uniprot-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.00041 | $0.00358 |
| Opus 5 | $0.00020 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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.
This is a copy
100% identical to ci-failure-triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CI Failure Triage
Follow AGENTS.md first.
Workflow
- Run
make ci-localand read the log to see which sub-target failed. It typically chainsformat-check lint-ci lint-loc typecheck test-fast test-integration, but repos vary (e.g.clinvar-linkhas nolint-loc) — trust the actual recipe/CI log, not this list. - Format (
format-check) — runmake format, re-check. - Lint (
lint-ci) — runmake lint-fix; fix remaining findings by hand rather than blanket-ignoring. - Line budget (
lint-loc, the per-file line budget inscripts/check_file_size.py, where present) — split the growing module along its seams; edit.loc-allowlistonly with a tracked decomposition reason. - Typecheck (
typecheck) — runmake typecheck; fix the type, don't add broadignore_errors/# type: ignore. - Tests (
test-fast/test-integration) — fix code or test per the assertion; parser/data changes need fixture-backed coverage undertests/. - Re-run
make ci-localuntil green before handoff.
Common mistakes
- Silencing lint/typecheck instead of fixing the cause.
- Bumping
.loc-allowlistto dodge a needed split. - Committing with a red
ci-local.
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 · 25 lines · 41 tokens per session scan A 11387ecb2276
ci-failure-triage is a skill published in the GitHub repository berntpopp/uniprot-link (0 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 358 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ci-failure-triage, differing in 0 lines, and is treated as a copy.
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"…