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/Arize-ai/phoenixWrote 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/arize-ai/phoenix/cloud-triage)<a href="https://agentmods.dev/agents/arize-ai/phoenix/cloud-triage"><img src="https://agentmods.dev/badge/agents/arize-ai/phoenix/cloud-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/agents/arize-ai/phoenix/cloud-triage"><img src="https://agentmods.dev/badge/agents/arize-ai/phoenix/cloud-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.00048 | $0.00552 |
| Opus 5.5 | $0.00019 | $0.00221 |
| Sonnet 5.5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
phoenix-cloud-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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago First seen · 32 lines · 48 tokens per session scan A 94363384a510
phoenix-cloud-triage is an agent published in the GitHub repository Arize-ai/phoenix (12,086 stars, last pushed today), with no licence file. It adds 48 tokens to every session and 552 once invoked, about $0.0002 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-10-29.
Other agents, from other repositories
openinference-issue-triager
Triages one new OpenInference issue - classifies and labels it by the issue-triage skill, has subagents reproduce it and locate its code path, grades whether there is enough information to start, finds the issue it duplicates, and submits the verdict and the reporter's open questions with submittriage. It never writes…
openinference-issue-analyst
Investigates one OpenInference issue for triage without changing code - locates the code path a fix or feature touches, checks whether it already shipped, finds the closest existing pattern and any decision a maintainer must make, says whether verifying it needs a live provider recording, and for an enhancement runs a…
evolve-scout-scan
MAP-step slice scanner for the scout map-reduce decomposition. Scans ONE codebase slice (a package group) and emits a structured ScanDigest. Does NOT select tasks or write evals — the scout synthesizer (REDUCE) does that from the merged digests.
incident-to-backlog-router
Automates routing of incident signals into prioritized backlog or maintenance work items with required portfolio fields pre-populated and closure linkage tracked. USE FOR: create GitHub issues from incident metadata with Type/Priority/Risk/Guardrail State/SRE Impact pre-filled, route incidents to sprint or maintenance…
bug-intake-refiner
A read-only bug-report editor that turns a raw issue into a short title and a concise issue brief, while listing constraints, unclear points, and up to three blocking questions.
tracker-collector
Incident-evidence collector for Jira. Given issue keys from the incident thread, reads tickets, comments, and status via jira-cli, checks for prior incidents with the same failure mode, and returns a compact evidence card. Never returns full issue bodies. Use as a Stage B collector spawned by /postmortem.