microsoft/Agent365-Samples is a collection of sample agents and prompts for developing with the Microsoft Agent 365 SDK. It is for developers building agents for Microsoft 365, Teams, Copilot Studio, Webchat, and related development environments in several programming languages. The catalogue entries are examples and instructions built around these samples.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-Samples. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Agent365-Samples/main/.claude/agents/sample-code-reviewer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-SamplesWrote 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/microsoft/agent365-samples/sample-code-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-samples/sample-code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-samples/sample-code-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/microsoft/agent365-samples/sample-code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-samples/sample-code-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.00292 | $0.01470 |
| Opus 5.5 | $0.00117 | $0.00588 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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 (112 stars, last pushed yesterday), licensed MIT. It adds 292 tokens to every session and 1,470 once invoked, about $0.0012 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.