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 sigistry/marketplace --skill gha-failure-taxonomygit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/gha-failure-taxonomy)<a href="https://agentmods.dev/skills/sigistry/marketplace/gha-failure-taxonomy"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/gha-failure-taxonomy/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/sigistry/marketplace/gha-failure-taxonomy"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/gha-failure-taxonomy.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.00083 | $0.00808 |
| Opus 5 | $0.00042 | $0.00404 |
| Sonnet 5 | $0.00017 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
gha-failure-taxonomy 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Failure Taxonomy
Purpose
A consistent way to classify a failing (or non-running) GitHub Actions workflow into one root-cause class, so triage goes straight from a log line to the exact YAML fix instead of trial-and-error re-runs. This is domain knowledge about how Actions actually breaks, not generic YAML advice.
First split: did it FAIL or never RUN?
- Never ran (no run appears, or the job count is 0): almost always the
on:trigger,paths/paths-ignore,branches/tagsfilter, or amatrixthat expanded to nothing. Do not look for a step error. - Ran and failed: anchor on the platform's error string, then classify below.
Classification matrix
| Class | Fastest log signal | Root cause | Fix direction |
|---|---|---|---|
| Permissions / token scope | Resource not accessible by integration, HTTP 403 |
GITHUB_TOKEN lacks a scope |
add least-privilege permissions: |
| Missing / misnamed secret | secret ... not found, empty var, auth 401 |
secret undefined, wrong name, or wrong scope (repo vs env) | define/rename secret; check environment |
| Matrix expansion | 0 jobs, or siblings cancelled | matrix typo or fail-fast: true |
fix matrix keys; fail-fast: false |
| Cache miss | Cache not found for input keys |
cache key drift / never saved | stabilize key, add restore-keys |
| Trigger mismatch | workflow absent from runs | on: / paths / branch filter |
widen or correct the filter |
| Checkout depth | shallow, missing tags, git describe fails |
default fetch-depth: 1 |
fetch-depth: 0 |
| Concurrency cancellation | Canceling since a higher priority |
concurrency with cancel |
expected; scope the group |
| Runner / tool drift | command not found, version mismatch |
runner image or tool changed | pin setup-* version / runner image |
| OIDC / cloud auth | sts:AssumeRoleWithWebIdentity denied |
missing id-token: write or trust policy |
add permission; fix cloud trust |
| Flaky / network | timeout, ECONNRESET, passes on re-run | external instability | retry/backoff, pin mirrors |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 44 lines · 83 tokens per session scan A f7098665d571
gha-failure-taxonomy is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 808 once invoked, about $0.0004 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
infra-standards
Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (a repo with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator that runs on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever a VERSION file…
devops
Use when setting up CI/CD pipelines, deploying applications, managing cloud infrastructure (AWS, GCP, Azure), implementing monitoring, containerizing services, or automating deployments with infrastructure as code.
ci-cd-pipeline
Use near the end of a project to generate CI and make the app deploy-ready. Produces a polyglot GitHub Actions workflow (lint, typecheck, test, build) and multi-stage Dockerfiles. The finish line is CI-green and container-ready, not an actual deploy.
infrastructure-planning
Plan and document the required software, infrastructure, and logistics for a Paperclip company — domains, GitHub, Docker Hub, Kubernetes, Slack, Google Workspace, Stripe, shipping providers, and CI/CD pipelines. Use when setting up infrastructure for a new company or auditing what an existing company needs.
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…