Borrowing it
Nothing to install: this file belongs to julianobarbosa/azure-finops-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/julianobarbosa/azure-finops-mcp-server/main/.claude/commands/bmadInfraDevOps/tasks/review-infrastructure.mdgit clone --depth 1 https://github.com/julianobarbosa/azure-finops-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/commands/julianobarbosa/azure-finops-mcp-server/review-infrastructure)<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/review-infrastructure"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/review-infrastructure/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/julianobarbosa/azure-finops-mcp-server/review-infrastructure"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/review-infrastructure.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.01798 |
| Opus 5 | $0.00000 | $0.00899 |
| Sonnet 5 | $0.00000 | $0.00360 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
review-infrastructure 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 11d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review-infrastructure Task
When this command is used, execute the following task:
Infrastructure Review Task
Purpose
To conduct a thorough review of existing infrastructure to identify improvement opportunities, security concerns, and alignment with best practices. This task helps maintain infrastructure health, optimize costs, and ensure continued alignment with organizational requirements.
Inputs
- Current infrastructure documentation
- Monitoring and logging data
- Recent incident reports
- Cost and performance metrics
infrastructure-checklist.md(primary review framework)
Key Activities & Instructions
1. Confirm Interaction Mode
- Ask the user: "How would you like to proceed with the infrastructure review? We can work: A. Incrementally (Default & Recommended): We'll work through each section of the checklist methodically, documenting findings for each item before moving to the next section. This provides a thorough review. B. "YOLO" Mode: I can perform a rapid assessment of all infrastructure components and present a comprehensive findings report. This is faster but may miss nuanced details."
- Request the user to select their preferred mode and proceed accordingly.
2. Prepare for Review
- Gather and organize current infrastructure documentation
- Access monitoring and logging systems for operational data
- Review recent incident reports for recurring issues
- Collect cost and performance metrics
- <critical_rule>Establish review scope and boundaries with the user before proceeding</critical_rule>
3. Conduct Systematic Review
- If "Incremental Mode" was selected:
- For each section of the infrastructure checklist:
- a. Present Section Focus: Explain what aspects of infrastructure this section reviews
- b. Work Through Items: Examine each checklist item against current infrastructure
- c. Document Current State: Record how current implementation addresses or fails to address each item
- d. Identify Gaps: Document improvement opportunities with specific recommendations
- e. Offer Advanced Self-Refinement & Elicitation Options
- f. Section Summary: Provide an assessment summary before moving to the next section
- For each section of the infrastructure checklist:
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.
- 11d ago First seen · 166 lines · 0 tokens per session scan A 267151bb9800
review-infrastructure is a command published in the GitHub repository julianobarbosa/azure-finops-mcp-server (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,798 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.