clingen-link: Skill for Claude Code

.claude/skills/ci-failure-triage/SKILL.md

ci-failure-triage is a skill for Claude Code from berntpopp/clingen-link. It costs 41 tokens per session (358 once invoked), scanned A, a copy of ci-failure-triage, MIT.

A troubleshooting guide for local and GitHub Actions checks that fail during formatting, linting, type checking, or testing.

In plain words
What is it for?
Use it when `make ci-local` fails or a GitHub Actions run is red. It covers formatting, lint fixes, file-size limits, type errors, and test failures.
Why use it?
It helps identify which check failed and gives a focused way to fix the underlying problem before handing off code.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is berntpopp/clingen-link's own configuration. It tells Claude Code how to work on clingen-link itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything clingen-link configures →

Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/clingen-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.

Copy the file
curl -O https://raw.githubusercontent.com/berntpopp/clingen-link/main/.claude/skills/ci-failure-triage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/berntpopp/clingen-link

Made for: Claude Code.

Wrote 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.

agentmods badge for ci-failure-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/berntpopp/clingen-link/ci-failure-triage/github.svg)](https://agentmods.dev/skills/berntpopp/clingen-link/ci-failure-triage)
Your own site
<a href="https://agentmods.dev/skills/berntpopp/clingen-link/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/clingen-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.

agentmods 80×15 button for ci-failure-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/berntpopp/clingen-link/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/clingen-link/ci-failure-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 358 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 11387ecb2276, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 11d 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.

Origin

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.

.claude/skills/ci-failure-triage/SKILL.md · 25 lines

What it actually says

CI Failure Triage

Follow AGENTS.md first.

Workflow

  1. Run make ci-local and read the log to see which sub-target failed. It typically chains format-check lint-ci lint-loc typecheck test-fast test-integration, but repos vary (e.g. clinvar-link has no lint-loc) — trust the actual recipe/CI log, not this list.
  2. Format (format-check) — run make format, re-check.
  3. Lint (lint-ci) — run make lint-fix; fix remaining findings by hand rather than blanket-ignoring.
  4. Line budget (lint-loc, the per-file line budget in scripts/check_file_size.py, where present) — split the growing module along its seams; edit .loc-allowlist only with a tracked decomposition reason.
  5. Typecheck (typecheck) — run make typecheck; fix the type, don't add broad ignore_errors / # type: ignore.
  6. Tests (test-fast / test-integration) — fix code or test per the assertion; parser/data changes need fixture-backed coverage under tests/.
  7. Re-run make ci-local until green before handoff.

Common mistakes

  • Silencing lint/typecheck instead of fixing the cause.
  • Bumping .loc-allowlist to dodge a needed split.
  • Committing with a red ci-local.
Changes

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.

  1. 11d ago First seen · 25 lines · 41 tokens per session scan A 11387ecb2276

Subscribe to this mod's changes

ci-failure-triage is a skill published in the GitHub repository berntpopp/clingen-link (0 stars, last pushed 7d 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.

Related

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.

Kevin-Liu-01/Agent-Machines · 72 tokens

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.

cyanheads/uniprot-mcp-server · 86 tokens

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.

cyanheads/gnomad-genetics-mcp-server · 54 tokens

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.

cyanheads/uniprot-mcp-server · 54 tokens

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.

cyanheads/uniprot-mcp-server · 52 tokens

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.

Tracer-Cloud/opensre · 48 tokens