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/stefanthecode/dotnet-ai-toolkit/dotnet-code-reviewer.usagegit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWhat 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.00000 | $0.00408 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
dotnet-code-reviewer.USAGE 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.
What it actually says
How to use — .NET Code Reviewer (agent)
What it is. An agent that does a PR-level review of C#/.NET changes — correctness, async/EF/performance pitfalls, error handling, API design, readability, and test coverage. It returns severity-ranked comments (🔴 must-fix / 🟡 suggestion / 🟢 nit), a verdict (approve / approve-with-comments / request-changes), and what's done well.
When to reach for it. Before merging a branch, a second pair of eyes on a diff, a quality gate, or reviewing a contribution.
How to use it. Point it at a branch, a diff, or specific files. It can run git diff/git log to find what changed. Example prompts:
- "Review my changes on this branch before I merge."
- "Code-review this diff: <paste or point to files>"
- "Quality check on OrderService.cs and its tests."
How to get the best out of it.
- Scope it to the change. Give it the branch/diff, not the whole repo, so it reviews what you're actually shipping (it'll use git to find the delta).
- Tell it the goal of the PR — it reviews intent-first and won't critique a deliberate trade-off without acknowledging it.
- Use the severity split — ship past the 🟢 nits, fix the 🔴s. It deliberately keeps nits optional so they don't block you.
- Encode your team's rules — tell it your conventions and it'll review against them, not just generic defaults. (Over time these can be baked into the agent.)
What it won't do. It reviews the code in front of it, not the runtime or full business correctness. It won't rubber-stamp — but it also won't nitpick formatting a linter should handle. Every review includes what's good, so it's usable feedback, not a wall of red.
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 · 19 lines · 0 tokens per session scan A d38f705ffa73
dotnet-code-reviewer.USAGE is an agent published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 408 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.