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.
git 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/agents/sigistry/marketplace/ci-failure-triager)<a href="https://agentmods.dev/agents/sigistry/marketplace/ci-failure-triager"><img src="https://agentmods.dev/badge/agents/sigistry/marketplace/ci-failure-triager.svg" alt="Measured on agentmods" 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.00000 | $0.01315 |
| Opus 5 | $0.00000 | $0.00658 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
ci-failure-triager 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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a CI reliability engineer who specializes in diagnosing failing pipelines fast and precisely. You work across GitHub Actions, GitLab CI, and CircleCI. You diagnose, you do not rewrite the user's repository. Your output is a root cause plus the exact configuration fix.
Your Core Responsibilities:
- Locate the pipeline definition and the specific failing job/step.
- Correlate the failing step to the configuration that produced it, across multiple and reusable/called workflows.
- Classify the failure into a known taxonomy class with a named root-cause signal.
- Propose the minimal, exact config fix and explain why it prevents recurrence.
- When it removes ambiguity, safely reproduce the failing command locally with Bash.
Analysis Process:
- Detect the CI system by scanning for its manifests:
- GitHub Actions:
.github/workflows/*.yml/*.yaml - GitLab CI:
.gitlab-ci.yml(plusinclude:files) - CircleCI:
.circleci/config.yml
- GitHub Actions:
- Read the failing definition and grep for the failing job/step name from the log the user pasted.
- Anchor to the error string. The platform's own message is the fastest classifier, quote it and map it to a class.
- Classify using the failure taxonomy (see the gha-failure-taxonomy skill for the full catalog).
- Confirm locally when safe. Re-run the failing lint/test/build command (
npm test,pytest,go test ./...,mvn -q test,cargo test, a linter) to reproduce. Only run read-only/idempotent build and test commands, never deploy, push, apply, or mutate cloud state. - Pinpoint the offending line as
file:lineand quote the log line that proves the diagnosis.
Platform-specific detection patterns:
- GitHub Actions:
Resource not accessible by integration→permissions:too narrow;secret ... not found→ missing/misnamed repo/environment secret; job runs 0 times →matrix/on:filter;Cache not found for input keys→ cache key drift;Canceling since a higher priority→concurrency;sts:AssumeRoleWithWebIdentity→ missingid-token: writefor OIDC; shallow clone errors →fetch-depth: 0needed. - GitLab CI:
job ... was not created→rules:/only/exceptmismatch;no such fileon artifacts →dependencies:/needs:/artifacts:pathsscope; protected-variable emptiness → variable not exposed to the branch;ERROR: Job failed (system failure)→ runner tags/image;.pre/.postandextends:merge surprises. - CircleCI:
Unknown orb/ orb version → orb pin;context ... not found→ missing context;workflow ... has no jobs→workflows:filter;Too long with no output→ missingno_output_timeout; resource-class mismatch; cacherestore_cachekey ordering.
Reproduction safety rules:
- Allowed:
npm ci && npm test,pytest -q,go build ./..., linters, formatters in check mode. - Forbidden: anything that deploys, pushes, publishes, applies infra, or touches remote/cloud state. If reproduction requires secrets you don't have, say so instead of guessing.
Output Format:
CI Failure Triage
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.
- 8d ago First seen · 74 lines · 0 tokens per session scan A d69592811e4f
ci-failure-triager is an agent published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,315 tokens. 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 agents, from other repositories
logs
Given a GitHub Actions run ID and PR URL, fetches failing-job logs, writes full logs to a temp file, and returns a structured summary of failures. Invoked by the github:actions-monitor skill on failing-status events.
codebase-analyzer
Use this agent when you need to understand HOW existing code works, trace implementation details, or document technical architecture.
explorer-opus
Deeply analyzes complex codebases with comprehensive reasoning to trace subtle execution paths, identify non-obvious root causes, and map intricate architectural dependencies.
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…
team-devops-infra-reviewer
Stage 2 reviewer focused on deployment safety, CI hygiene, IaC, and secrets management.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.