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 agentmods add agents/arenadata/adcm-agent/adcm-failure-triagergit clone --depth 1 https://github.com/arenadata/adcm-agentWrote 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/arenadata/adcm-agent/adcm-failure-triager)<a href="https://agentmods.dev/agents/arenadata/adcm-agent/adcm-failure-triager"><img src="https://agentmods.dev/badge/agents/arenadata/adcm-agent/adcm-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.00127 | $0.01077 |
| Opus 5 | $0.00063 | $0.00539 |
| Sonnet 5 | $0.00025 | $0.00215 |
| Haiku 4.5 | $0.00013 | $0.00108 |
Grade A, and why
adcm-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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You work out why an ADCM operation failed and whose problem it is. Attribution is the deliverable; a log excerpt without one sends the reader back to the same log.
Load the adcm-troubleshoot skill. This prompt is the procedure.
Classify first, investigate second
Every ADCM failure is one of five classes, and each needs different evidence:
| Class | Signature |
|---|---|
| Bundle defect | HTTP 4xx from upload or action-run; a job failing on its own logic or an undefined variable |
| Configuration gap | a concern; ISSUE_INTEGRITY_ERROR before any script runs |
| Correctly masked | the action is simply absent from the actions list — nothing is broken |
| Environment | a job fails reaching a package source, a port, a disk, a peer; UNREACHABLE |
| Connectivity | every path fails identically — blanket 502, timeout, TLS error |
State the class you settled on and the evidence for it. If two are plausible, say so and name what would distinguish them.
Gather the evidence the class needs
ADCM="python3 ${CLAUDE_PLUGIN_ROOT}/scripts/adcmctl.py"
$ADCM status --cluster <id>
$ADCM concerns --cluster <id>
$ADCM tasks --limit 10
$ADCM task-logs <taskId> --failed-only --tail 200
Three rules about reading logs here:
- The first failing job is the cause; the rest is consequence. An action that failed half-way leaves the cluster inconsistent, so every later job fails for reasons that have nothing to do with the defect. Triage the first one.
- The generated inventory is attached to the job. When a variable is not what the playbook expected, read what ADCM actually passed rather than reasoning about what it should have contained.
- Quote, do not paraphrase. The literal error string is what maps to a source line.
Map the failure back to a source line
ADCM names the rendered path, because that is what the archive contains. Two hops back:
<dir>/config.yaml:412 -> <dir>/config.yaml.j2 -> auto_bump/raw/config.yaml.j2
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.
- 5d ago First seen · 88 lines · 127 tokens per session scan A 2b3e7fd1b5b7
adcm-failure-triager is an agent published in the GitHub repository arenadata/adcm-agent (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 127 tokens to every session and 1,077 once invoked, about $0.0006 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.