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/Azure-Samples/pizza-mcp-agentsWrote 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/commands/azure-samples/pizza-mcp-agents/review-and-refactor)<a href="https://agentmods.dev/commands/azure-samples/pizza-mcp-agents/review-and-refactor"><img src="https://agentmods.dev/badge/commands/azure-samples/pizza-mcp-agents/review-and-refactor/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/commands/azure-samples/pizza-mcp-agents/review-and-refactor"><img src="https://agentmods.dev/badge/commands/azure-samples/pizza-mcp-agents/review-and-refactor.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.00000 | $0.00129 |
| Opus 5 | $0.00000 | $0.00064 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
review-and-refactor 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 4d 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
Role
You're a senior expert software engineer with extensive experience in maintaining projects over long time and ensuring clean code and best practices.
Task
- Take a deep breath, and review all coding guidelines instructions in
.github/instructions/*.mdand.github/copilot-instructions.md, then review all the code carefully and make code refactorings if needed. - The final code should be clean and maintainable while following the specified coding standards and instructions.
- You can split up the code, rename files or create new files if needed.
- If the project includes tests, ensure they are still passing after your changes.
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.
- 4d ago First seen · 11 lines · 0 tokens per session scan A ddd0586ec705
review-and-refactor is a command published in the GitHub repository Azure-Samples/pizza-mcp-agents (33 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 129 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-09-06.
Other commands, from other repositories
full-review
Orchestrate comprehensive multi-dimensional code review using specialized review agents across architecture, security, performance, testing, and best practices.
pre-merge-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de merger une branche, pour garantir la qualité et éviter les régressions.
qa
QA sign-off command. Verifies a change against acceptance criteria, runs the test suite, probes edge cases, and issues a ship / no-ship verdict via the qa-lead agent.
codex-loop
Use Codex as a second, differently-trained reviewer of your branch, fix every real finding with regression tests, and loop until two consecutive reviews come back clean. Runs autonomously.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
orch-refine-code
Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Wrapper for the orch-refine-code skill.