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 fall-out-bug/sdp --skill ci-triagegit clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/ci-triage)<a href="https://agentmods.dev/skills/fall-out-bug/sdp/ci-triage"><img src="https://agentmods.dev/badge/skills/fall-out-bug/sdp/ci-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/fall-out-bug/sdp/ci-triage"><img src="https://agentmods.dev/badge/skills/fall-out-bug/sdp/ci-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.00023 | $0.00408 |
| Opus 5.5 | $0.00009 | $0.00163 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
ci-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 1mo 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.
What it actually says
CI Triage
Use this skill when a branch or PR has failing CI and you need fast root-cause with actionable follow-up.
Inputs
- PR number or URL (preferred)
- Or branch name (e.g.
feature/<feature-id>)
Workflow
1) Collect CI signal
gh pr checks <pr-number>
gh run list --branch <branch> --limit 20
2) Identify failing runs and jobs
gh run view <run-id>
gh run view <run-id> --log-failed
If logs are missing, query run metadata and check-suite details:
gh api repos/<owner>/<repo>/actions/runs/<run-id>
gh api repos/<owner>/<repo>/actions/runs/<run-id>/jobs
3) Classify root cause
Pick one primary class:
- Workflow config issue
- Test/regression failure
- Environment/dependency drift
- Permissions/secrets issue
- Flaky/infra transient
4) Propose smallest safe fix
- Point to exact workflow/job/step
- Provide command-level repro if possible
- Suggest one patch path and one fallback
5) Track in Beads
Create a follow-up item when CI is not green:
bd create --title="CI: <short root cause>" --type=bug --priority=1
bd dep add <new-id> <parent-feature-id>
bd sync
Output Template
## CI Triage Result
- Branch/PR: ...
- Failing workflow(s): ...
- Root cause: ...
- Evidence: run/job/step links
- Proposed fix: ...
- Beads follow-up: <id>
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.
- 1mo ago First seen · 77 lines · 23 tokens per session scan A 3955c4775dca
ci-triage is a skill published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 408 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
GitHub CI Fix Debugging
Debug and fix failing GitHub PR checks by inspecting GitHub Actions logs, summarizing failure context, drafting fix plans, and implementing fixes after approval.
github-actions-debugger
Debug and monitor GitHub Actions workflow runs. Check run status, view failed job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitHub Actions failures, inspect job output, or identify the root cause of a broken workflow run.
gitlab-pipeline-debugger
Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs.
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks", "update megalinter skills". Always goes through npx mega-linter-runner…
gh-fix-ci
Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose a plan, and only implement after explicit user approval. External CI providers (Buildkite, CircleCI, etc.) are reported by URL only.
ArgoCD Sync Troubleshooter
Diagnoses ArgoCD application sync failures using the ArgoCD REST API and Kubernetes resource diff analysis. Identifies Helm value conflicts, Kustomize overlay errors, and resource health check failures.