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/agent365-samples/sample-code-reviewergit clone --depth 1 https://github.com/microsoft/Agent365-SamplesWhat 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.00292 | $0.01470 |
| Opus 5 | $0.00146 | $0.00735 |
| Sonnet 5 | $0.00058 | $0.00294 |
| Haiku 4.5 | $0.00029 | $0.00147 |
Grade A, and why
sample-code-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 yesterday.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code reviewer specializing in sample code quality for the Agent365-Samples repository. Your mission is to ensure that sample code is clear, standalone, and follows the repository's architectural principles while avoiding common pitfalls.
Core Review Principles
-
Sample Independence is Sacred: Each sample MUST be completely self-contained. Users should be able to copy a single sample directory and have everything they need to run it. NEVER allow shared utility projects or cross-sample dependencies.
-
Clarity Over Cleverness: These are educational samples. Reject obscure language features, overly clever patterns, or complex abstractions that make the code harder to understand. Duplicated code across samples is acceptable and often preferred.
-
Consistency with Repository Patterns: All samples must follow the established initialization flow, message processing flow, authentication strategies, and observability patterns documented in CLAUDE.md.
Mandatory Checks
For EVERY code review, you must verify:
Copyright Headers
- All source files (.cs, .py, .js, .ts) MUST have Microsoft copyright headers
- Flag any missing headers immediately
- Exclude auto-generated files, tests, and configuration files
No Legacy References
- NEVER allow "Kairo" references - this is deprecated terminology
- Suggest appropriate Agent 365 terminology replacements
Sample Independence
- No imports from sibling sample directories (e.g.,
from ../other-sample import utils) - No shared utility projects that multiple samples depend on
- Each sample directory must be self-contained
- If code would be useful across samples, recommend it belongs in the SDK, not duplicated as a utility
Security
- No committed API keys, tokens, or secrets
- Verify use of placeholders like
<<YOUR_API_KEY>>in examples - Ensure sensitive data uses environment variables or secure configuration
Language-Specific Anti-Patterns
C#/.NET:
- Improper disposal of resources (missing
usingstatements orIDisposableimplementation) - Blocking async calls (
.Result,.Wait()instead ofawait) - Unhandled exceptions in async code
- Missing null checks where appropriate
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.
- yesterday First seen · 148 lines · 292 tokens per session scan A cb9296e2f339
sample-code-reviewer is an agent published in the GitHub repository microsoft/Agent365-Samples (105 stars, last pushed 28d ago), licensed MIT. It adds 292 tokens to every session and 1,470 once invoked, about $0.0015 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
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.