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/0gis0/ado_codingagent/azdo-failure-triagegit clone --depth 1 https://github.com/0GiS0/ADO_CodingAgentWrote 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/0gis0/ado_codingagent/azdo-failure-triage)<a href="https://agentmods.dev/agents/0gis0/ado_codingagent/azdo-failure-triage"><img src="https://agentmods.dev/badge/agents/0gis0/ado_codingagent/azdo-failure-triage.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 | $0.00034 | $0.00248 |
| Opus 5 | $0.00017 | $0.00124 |
| Sonnet 5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
π§― AzDO Failure 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 Β· 36 lines Β· 34 tokens per session scan A f28c8ad9c89d
π§― AzDO Failure Triage is an agent published in the GitHub repository 0GiS0/ADO_CodingAgent (2 stars, last pushed 1mo ago), with no licence file. It adds 34 tokens to every session and 248 once invoked, about $0.0002 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
FabricReleaseEngineer
Plan and execute Microsoft Fabric release engineering across Git integration, deployment pipelines, Variable Libraries, Fabric REST APIs, fabric-cicd, GitHub Actions, Azure DevOps, validation gates, rollback, and post-deploy smoke tests. Use when the request involves deploy, promote, release, CI/CD, ALMβ¦
refactorer
Specialized ADVPL/TLPP refactoring agent - analyzes code structure and suggests safe improvements without changing behavior.
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only β authors nothing.
coding
You are an expert coding engineer working with the user. You produce high quality code and artifacts on behalf of the user. You operate as an implementation specialist.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
discussion-spec
μμ μΌμ§κ° 무μμ νλ(νκ³ ), νλλκ° λ¬΄μμ, μ΄λκΉμ§(κ²°μ ν κ³ν)λΌλ©΄, λ¬Έμ ν΄κ²° λ¬Έμ(.oculpm/discussion/ /discussion.md)λ κ·Έ μ λ¨κ³ β "μ΄κ² λ¬Έμ μΈκ°? μ΄λ€ μλ€μ΄ μλ?" λ₯Ό κ²°μ μ μ μ 리νλ νμλ‘μ λλ€.