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 cloudbees-oss/devops-agent-kit --skill triagegit clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kitWrote 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/cloudbees-oss/devops-agent-kit/triage)<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/triage"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/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/cloudbees-oss/devops-agent-kit/triage"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/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.00033 | $0.00522 |
| Opus 5.5 | $0.00013 | $0.00209 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
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
Triage Failed Run: $ARGUMENTS
-
Search for the component using
components_search -
Pull recent runs using
runs_list(limit=10) -
Filter for FAILED runs. Skip any with workflow names containing "code_scan"
-
For the latest failed run: a.
automation_jobs_list— list all jobs and their statuses b. For each failed job, identify the failing step c.logs_list— attempt to pull logs from the failing step NOTE: If this returns a 500 error, proceed without logs. Analyze based on step names, statuses, and durations instead. d.workflow_get_content— read the workflow YAML to understand what each step does and identify configuration issues -
Classify the failure:
- CONFIG: Workflow/pipeline configuration error (missing inputs, invalid action references, YAML syntax). Look for validation errors.
- CODE: Compilation failure or test failure caused by a code change. Check if earlier steps (build, compile) passed.
- SECURITY: Security scan gate failure (Gitleaks, SAST, SCA).
Cross-reference with
security_findings_summary_get. - ENVIRONMENT: Infrastructure issue — timeouts, connection refused, resource exhaustion, runner unavailability.
- KNOWN: Matches a pattern from previous triage (same step, same error).
-
Enrich with security context: a.
security_findings_summary_get— check if the component has open security findings that may be related to the failure -
Present a structured triage report:
- Run ID, workflow name, trigger, timestamp
- Step-by-step results table (step name, status, duration)
- Root cause analysis with specific evidence
- Classification (CONFIG/CODE/SECURITY/ENVIRONMENT/KNOWN)
- Fix recommendation
-
Offer next actions:
- File a Jira ticket for the issue (
/file-ticket) - Post the summary to Slack
- Comment on the relevant GitHub PR
- If the fix is a workflow config change, offer to apply it via
workflow_update_content(with user confirmation)
- File a Jira ticket for the issue (
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 · 51 lines · 33 tokens per session scan A b06fbd15c02b
triage is a skill published in the GitHub repository cloudbees-oss/devops-agent-kit (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 522 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-31.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.