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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/azure-verified-modules-owner-triage)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/azure-verified-modules-owner-triage"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/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.
<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/azure-verified-modules-owner-triage"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/azure-verified-modules-owner-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.00061 | $0.10312 |
| Opus 5 | $0.00030 | $0.05156 |
| Sonnet 5 | $0.00012 | $0.02062 |
| Haiku 4.5 | $0.00006 | $0.01031 |
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 10d 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)' This is a copy
100% identical to AVM Owner Triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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, andazurerm-vs-azapigaps that the thread alone can't reveal.Present the choice exactly like this:
"Before I start: do you want a
quicktriage (thread-only, faster) or adeeptriage (clones the repos and validates claims against upstream schema, slower but catches false bugs and real dependency chains)? Replyquickordeep."Record the choice in the report header so the consumer can see at a glance which mode produced the output. In
quickmode, 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)
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.
- 10d ago First seen · 683 lines · 61 tokens per session scan A fdd6a110c328
AVM Owner Triage is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 6d ago), licensed ISC. It adds 61 tokens to every session and 10,312 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to AVM Owner Triage, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.