AVM Owner Triage

AVM Owner Triage is an agent for Claude Code from github/awesome-copilot. It costs 61 tokens per session (10,312 once invoked), scanned A, original, MIT.

An agent for sorting open GitHub issues across Azure Verified Modules repositories that a particular owner maintains. Azure Verified Modules are reusable, Microsoft-reviewed infrastructure modules for deploying Azure resources.

In plain words
What is it for?
Use it to collect an owner’s open issues, analyze their dependencies, produce a triage report, and calculate the delegation ratio.
Why use it?
It separates issues that may be suitable for Copilot delegation from those needing human attention, while preserving owner control over comments and assignments.

Agent for Claude Code ✓ vendor

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter; mentions subagents; positional $N argument.

Good fit Use it to collect an owner’s open issues, analyze their dependencies, produce a triage report, and calculate the delegation ratio.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/github/awesome-copilot/azure-verified-modules-owner-triage
About the project

Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.

github/awesome-copilot · 40,159 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot

Made for: Claude Code.

Wrote 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.

agentmods badge for AVM Owner Triage

README.md
[![agentmods](https://agentmods.dev/badge/agents/github/awesome-copilot/azure-verified-modules-owner-triage/github.svg)](https://agentmods.dev/agents/github/awesome-copilot/azure-verified-modules-owner-triage)
Your own site
<a href="https://agentmods.dev/agents/github/awesome-copilot/azure-verified-modules-owner-triage"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/azure-verified-modules-owner-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.

agentmods 80×15 button for AVM Owner Triage

Your own site · 80×15
<a href="https://agentmods.dev/agents/github/awesome-copilot/azure-verified-modules-owner-triage"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/azure-verified-modules-owner-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 10,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00061 $0.10312
Opus 5.5 $0.00024 $0.04125
Sonnet 5.5 $0.00012 $0.02062
Haiku 4.5 $0.00006 $0.01031

Measured 1mo ago against content hash fdd6a110c328, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

AVM Owner Triage scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sS "$BASE/$f" | awk -v a="<OWNER_ALIAS>" -F',' 'NR==1 || tolower($0) ~ tolower(a)'
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

agents/azure-verified-modules-owner-triage.agent.md · 683 lines

How it starts

The opening of the file, as written. The whole thing — 683 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AVM Owner Triage Agent

❗ Step 0 - Ask for the owner alias. Before doing anything else, the agent MUST ask the user for their GitHub handle (the alias shown as the module owner in the AVM index, e.g. octocat). All subsequent discovery, harvesting, and reporting runs against that alias. Do not assume; do not carry over an alias from a previous session.

❓ Step 0.5 - Ask for the analysis depth. Immediately after the alias is confirmed and the module list is presented, the agent MUST ask the user to choose one of two modes:

  • quick (default) - Thread-only triage. Skip Section 2d (shallow clones), Section 5 Pass 1 (code-delta), and Section 5 Pass 2 (upstream-schema delta). Dependencies come from issue threads alone. Faster (minutes), lower-fidelity, fine for a first-pass weekly sweep. Acceptable risk: some "Copilot-ready" items may turn out to need design work once a human opens the code.
  • deep - Full three-pass dependency analysis. Clones every module, greps for code-surface overlaps per issue (Pass 1), validates property/feature claims against the upstream ARM/Bicep/Terraform schema (Pass 2), then does thread analysis (Pass 3). Slower (tens of minutes per 10-20 issues) but produces audit-grade dependency chains and catches false bugs, preview-API traps, and azurerm-vs-azapi gaps that the thread alone can't reveal.

Present the choice exactly like this:

"Before I start: do you want a quick triage (thread-only, faster) or a deep triage (clones the repos and validates claims against upstream schema, slower but catches false bugs and real dependency chains)? Reply quick or deep."

Record the choice in the report header so the consumer can see at a glance which mode produced the output. In quick mode, all references to "Pass 1 evidence", "Pass 2 evidence", or "code surface" in the report template collapse to "thread-claimed" and the corresponding columns state "(quick mode - not analysed)" rather than fabricating evidence.

Version: 1.6 (2026-04-24)


Read the full file on GitHub · 683 lines

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. 1mo ago First seen · 683 lines · 61 tokens per session scan A fdd6a110c328

Subscribe to this mod's changes

AVM Owner Triage is an agent published in the GitHub repository github/awesome-copilot (40,159 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 10,312 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.