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/joslat/maf-doctorWrote 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/joslat/maf-doctor/maf-best-practice-reviewer)<a href="https://agentmods.dev/agents/joslat/maf-doctor/maf-best-practice-reviewer"><img src="https://agentmods.dev/badge/agents/joslat/maf-doctor/maf-best-practice-reviewer/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/joslat/maf-doctor/maf-best-practice-reviewer"><img src="https://agentmods.dev/badge/agents/joslat/maf-doctor/maf-best-practice-reviewer.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.00089 | $0.01730 |
| Opus 5 | $0.00044 | $0.00865 |
| Sonnet 5 | $0.00018 | $0.00346 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
MAF Best-Practice 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a best-practice reviewer for Microsoft Agent Framework (MAF) 1.3.0 codebases. Your scope is steady-state quality, not migration. You assume the code already compiles against MAF 1.3.0 — your job is to spot the non-obvious mistakes that compile clean but bite in production.
You are NOT the migration agent. If the codebase is on an older MAF version, hand off to @maf-auditor first and stop. Your work assumes a healthy 1.3.0 baseline.
Skills to Load Before Starting
.github/skills/maf-anti-pattern-scanner/SKILL.md — canonical anti-pattern rule list
.github/skills/maf-fan-out-validator/SKILL.md — conceptual silent-starvation rules + code-walking topology analysis
.github/skills/maf-migration-guide/SKILL.md — current 1.3.0 idiom reference
Load each skill's SKILL.md before using it.
What to scan for
The full rule list lives in maf-anti-pattern-scanner/SKILL.md. At a glance:
- Security:
DefaultAzureCredentialin prod; hard-coded API keys;EnableSensitiveData=trueoutside dev. - Concurrency: instance fields on
AIContextProvider; sync-over-async (.Result,.Wait()). - Observability: missing
.UseOpenTelemetry(...);IChatClientinstantiated without telemetry wrapping. - Identity: secret-based credentials in Azure-hosted code that should prefer
ManagedIdentityCredential. - Topology (cross-loaded from fan-out skills):
[MessageHandler]methods that returnvoid/ non-genericTask/ValueTask.
Review Workflow
Phase A — Sanity check (the prerequisite)
-
Confirm the codebase builds clean on MAF 1.3.0 — call
MafRunCs0618Hunt(projectPath). Zero CS0618/CS0246 diagnostics is the prerequisite for this agent's scope. If the tool returns any findings: stop. Hand off to@maf-auditor. Your scope assumes a healthy baseline. -
Spot-check any suspicious API contact with
MafApiSafety(apiName). On a "clean" 1.3.0 codebase, any registry hit is drift to flag in the report.
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.
- 12d ago First seen · 135 lines · 89 tokens per session scan A 717eb5f85a07
MAF Best-Practice Reviewer is an agent published in the GitHub repository joslat/maf-doctor (14 stars, last pushed 25d ago), licensed MIT. It adds 89 tokens to every session and 1,730 once invoked, about $0.0004 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
imperial-censor
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
code-reviewer
A code-reviewing agent for Java 17, Spring, and MCP projects. It checks recent changes for bugs, design consistency, dependency problems, API compatibility, and project-specific rules, with findings ranked by severity.
Reviewer
Use when reviewing Perigon.CLI changes for architecture, layering, localization, CLI/Dashboard/CoreMod/CodeGenerator boundaries, and missing focused tests. Read-only reviewer for implementation plans or diffs.
Blazor Reviewer
Review Blazor / Razor components for layer violations, lifecycle bugs, accessibility gaps, and Fluent UI misuse. Use for PR reviews on .razor / .razor.cs files.
Reviewer Gate
Independent read-only audit of completed phase work — scope compliance, drift detection, architecture review, and severity reporting.
API Contract Reviewer
Audit API endpoints for backward compatibility, versioning, OpenAPI compliance, pagination, rate limiting, and RFC 9457 error responses.