genefoundry-router: Skill for Claude Code

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

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

A guide for diagnosing failed local checks or GitHub Actions runs. GitHub Actions is GitHub’s service for automatically running formatting, linting, type checks, and tests.

In plain words
What is it for?
Use it to investigate formatting, lint, file-size, type-checking, and test failures, then rerun the project’s local CI checks until they pass.
Why use it?
It helps you identify which automated check failed and choose a targeted fix instead of ignoring the error or weakening the check.

Skill for Claude Code

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

This is berntpopp/genefoundry-router's own configuration. It tells Claude Code how to work on genefoundry-router 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 genefoundry-router configures →

Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/genefoundry-router. 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/genefoundry-router/main/.claude/skills/ci-failure-triage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/berntpopp/genefoundry-router

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/genefoundry-router/ci-failure-triage/github.svg)](https://agentmods.dev/skills/berntpopp/genefoundry-router/ci-failure-triage)
Your own site
<a href="https://agentmods.dev/skills/berntpopp/genefoundry-router/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/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/genefoundry-router/ci-failure-triage"><img src="https://agentmods.dev/badge/skills/berntpopp/genefoundry-router/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 original No closer match found 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-11, 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

Copies of this mod

5 near-identical copies found in the catalogue:

.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/genefoundry-router (5 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

plano-observability-debugging

Improve Plano tracing and debugging workflows. Use for sampling strategy, span attributes, and trace query-based root-cause analysis.

katanemo/plano · 32 tokens

alterlab-link-health

Audits and repairs Markdown link health across a skills repo via a four-tier pipeline (config hardening, intra-repo file-ref fixes, external URL substitutions, residual exclusions) and enforces a Tier 3 substitution guardrail that prevents regressions of previously-passing links; designed for lychee-based GitHub…

AlterLab-IEU/AlterLab-Academic-Skills · 160 tokens

aevatar-triage

Use after an Aevatar workflow, codexexec call, schedule, channel, connector, skill, Agent Profile, or control-plane request fails or behaves unexpectedly. It applies when the agent must attribute the first broken boundary across Aevatar, NyxID, Ornn, chrono-sandbox/gVisor, the managed runner, or private SSH…

ChronoAIProject/NyxID · 119 tokens

nonlinear-solvers

Select and configure nonlinear solvers for f(x)=0 or min F(x). Use for Newton methods, quasi-Newton (BFGS, L-BFGS), Broyden, Anderson acceleration, diagnosing convergence issues, choosing line search vs trust region, and analyzing Jacobian quality.

beita6969/ScienceClaw · 63 tokens

linear-solvers

Select and configure linear solvers for systems Ax=b in dense and sparse problems. Use when choosing direct vs iterative methods, diagnosing convergence issues, estimating conditioning, selecting preconditioners, or debugging stagnation in GMRES/CG/BiCGSTAB.

beita6969/ScienceClaw · 55 tokens

numerical-stability

Analyze and enforce numerical stability for time-dependent PDE simulations. Use when selecting time steps, choosing explicit/implicit schemes, diagnosing numerical blow-up, checking CFL/Fourier criteria, von Neumann analysis, matrix conditioning, or detecting stiffness in advection/diffusion/reaction problems.

beita6969/ScienceClaw · 61 tokens