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/microsoft/foundry-local/reviewergit clone --depth 1 https://github.com/microsoft/foundry-localWhat 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.00042 | $0.02049 |
| Opus 5 | $0.00021 | $0.01025 |
| Sonnet 5 | $0.00008 | $0.00410 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
Reviewer 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 2d 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.
- 2d ago First seen · 148 lines · 42 tokens per session scan A 459386253f02
Reviewer is an agent published in the GitHub repository microsoft/foundry-local (2,532 stars, last pushed 2d ago), with no licence file. It adds 42 tokens to every session and 2,049 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-30.
Other agents, from other repositories
write-tests-agent
Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.
sandbox-agent
Specialized agent for working with the .NET MAUI Sandbox app for testing, validation, and experimentation.
custom-client
Use this path to evaluate models from a different provider or write a custom tool-calling agent. STATE-Bench does not ship third-party adapters — provider integration is user-owned.
ab900-cert-buddy-agent
AB-900 practice buddy: exam-realistic items + admin scenario walkthroughs, grounded in Microsoft Learn via Microsoft Learn MCP, Context7, and MarkItDown.
exploit-developer
Exploit and payload developer — writes custom exploits, reverse shells, bypasses, and PoCs for discovered vulnerabilities. Specializes in turning vulnerability findings into working attack code.
qa
Agent "qa" from Miosa-osa/OSA, covering qa — qa / security, default territory, responsibilities, does not touch and relationships.