Borrowing it
Nothing to install: this file belongs to juyamagu/azure-updates-mcp-server. 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/juyamagu/azure-updates-mcp-server/main/.github/agents/review-code.agent.mdgit clone --depth 1 https://github.com/juyamagu/azure-updates-mcp-serverWrote 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/juyamagu/azure-updates-mcp-server/review-code)<a href="https://agentmods.dev/agents/juyamagu/azure-updates-mcp-server/review-code"><img src="https://agentmods.dev/badge/agents/juyamagu/azure-updates-mcp-server/review-code/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/juyamagu/azure-updates-mcp-server/review-code"><img src="https://agentmods.dev/badge/agents/juyamagu/azure-updates-mcp-server/review-code.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.00021 | $0.01768 |
| Opus 5.5 | $0.00008 | $0.00707 |
| Sonnet 5.5 | $0.00004 | $0.00354 |
| Haiku 4.5 | $0.00002 | $0.00177 |
Grade A, and why
review-code 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 2mo 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
-
Initialize Review Context:
- Run
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksfrom repo root - Parse FEATURE_DIR and AVAILABLE_DOCS from output
- Identify the feature scope and related artifacts
- Run
-
Collect Git Changes:
- Use
get_changed_filesto retrieve all staged and unstaged changes - Parse the diff output to identify:
- New files created
- Modified files
- Deleted files
- Lines added/removed per file
- Categorize changes by type: source code, tests, documentation, configuration
- Use
-
Load Reference Artifacts:
- REQUIRED: Read tasks.md to understand what was supposed to be implemented
- REQUIRED: Read spec.md for feature requirements and acceptance criteria
- IF EXISTS: Read plan.md for architecture and design decisions
- IF EXISTS: Read contracts/ for API specifications
- IF EXISTS: Read data-model.md for entity definitions
- IF EXISTS: Read checklists/ for quality checkpoints
-
Code Quality Review:
-
Style and Conventions:
- Check for consistent naming conventions (camelCase, PascalCase, snake_case)
- Verify proper indentation and formatting
- Identify unused imports or variables
- Check for hardcoded values that should be constants/config
-
Code Structure:
- Verify proper separation of concerns
- Check for appropriate error handling (try-catch, error types)
- Identify overly complex functions (>50 lines, high cyclomatic complexity)
- Verify proper use of async/await patterns
- Check for proper resource cleanup (connections, streams, timers)
-
Security and Best Practices:
- Check for exposed secrets or credentials in code
- Verify input validation and sanitization
- Check for SQL injection or XSS vulnerabilities
- Verify proper authentication/authorization checks
- Check for insecure dependencies or known CVEs
-
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.
- 2mo ago First seen · 225 lines · 21 tokens per session scan A 9af3b9b437cc
review-code is an agent published in the GitHub repository juyamagu/azure-updates-mcp-server (0 stars, last pushed 10mo ago), licensed MIT. It adds 21 tokens to every session and 1,768 once invoked, about $0.0001 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-31.
Other agents, from other repositories
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.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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.