ci-triage

A command for investigating failed GitHub Actions runs. GitHub Actions is GitHub's service for automatically running tasks such as tests and builds.

In plain words
What is it for?
Use it to examine failed workflow runs, identify the root cause, and create a Beads follow-up.
Why use it?
It turns a failed automated run into an evidence-based explanation of the cause and a tracked follow-up task.

Command

Install

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.

agentmods
npx agentmods add commands/fall-out-bug/sdp/ci-triage
Clone the repo
git clone --depth 1 https://github.com/fall-out-bug/sdp
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00018 $0.00160
Opus 5 $0.00009 $0.00080
Sonnet 5 $0.00004 $0.00032
Haiku 4.5 $0.00002 $0.00016

Measured 3d ago against content hash fd2ec01097e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

prompts/commands/ci-triage.md · 33 lines

What it actually says

/ci-triage — Ci-triage

Overview

This command implements the ci-triage skill from the SDP workflow.

See /prompts/skills/ci-triage/SKILL.md for complete documentation.

Usage

/ci-triage [arguments]

Implementation

The command delegates to the ci-triage skill, which provides:

  • Systematic workflow
  • Quality gates
  • Proper error handling
  • Documentation
  • Skills: prompts/skills/ci-triage/SKILL.md
  • Agents: prompts/agents/builder.md
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. 3d ago First seen · 33 lines · 18 tokens per session scan A fd2ec01097e8

Subscribe to this mod's changes

ci-triage is a command published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 160 once invoked, about $0.0001 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-30.