azure-finops-mcp-server: Command for Claude Code

.claude/commands/BMad/tasks/create-doc.md

create-doc is a command for Claude Code from julianobarbosa/azure-finops-mcp-server. It costs 0 tokens per session (889 once invoked), scanned A, a copy of create-doc, MIT.

An interactive workflow for creating a document from a YAML template, a structured configuration file that defines the document sections.

In plain words
What is it for?
Use it to discover an available template, complete each section with the user, and produce a document based on that template.
Why use it?
It prevents important sections and decisions from being skipped by requiring step-by-step discussion and user feedback.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is julianobarbosa/azure-finops-mcp-server's own configuration. It tells Claude Code how to work on azure-finops-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything azure-finops-mcp-server configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/julianobarbosa/azure-finops-mcp-server/main/.claude/commands/BMad/tasks/create-doc.md
Clone the repo
git clone --depth 1 https://github.com/julianobarbosa/azure-finops-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for create-doc

README.md
[![agentmods](https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/create-doc/github.svg)](https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/create-doc)
Your own site
<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/create-doc"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/create-doc/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.

agentmods 80×15 button for create-doc

Your own site · 80×15
<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/create-doc"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/create-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00889
Opus 5 $0.00000 $0.00445
Sonnet 5 $0.00000 $0.00178
Haiku 4.5 $0.00000 $0.00089

Measured 9d ago against content hash 5c754bff9346, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

create-doc 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 9d 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.

Origin

This is a copy

97% identical to create-doc — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/BMad/tasks/create-doc.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/create-doc Task

When this command is used, execute the following task:

Create Document from Template (YAML Driven)

⚠️ CRITICAL EXECUTION NOTICE ⚠️

THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL

When this task is invoked:

  1. DISABLE ALL EFFICIENCY OPTIMIZATIONS - This workflow requires full user interaction
  2. MANDATORY STEP-BY-STEP EXECUTION - Each section must be processed sequentially with user feedback
  3. ELICITATION IS REQUIRED - When elicit: true, you MUST use the 1-9 format and wait for user response
  4. NO SHORTCUTS ALLOWED - Complete documents cannot be created without following this workflow

VIOLATION INDICATOR: If you create a complete document without user interaction, you have violated this workflow.

Critical: Template Discovery

If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.

CRITICAL: Mandatory Elicitation Format

When elicit: true, this is a HARD STOP requiring user interaction:

YOU MUST:

  1. Present section content
  2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
  3. STOP and present numbered options 1-9:
    • Option 1: Always "Proceed to next section"
    • Options 2-9: Select 8 methods from data/elicitation-methods
    • End with: "Select 1-9 or just type your question/feedback:"
  4. WAIT FOR USER RESPONSE - Do not proceed until user selects option or provides feedback

WORKFLOW VIOLATION: Creating content for elicit=true sections without user interaction violates this task.

NEVER ask yes/no questions or use any other format.

Processing Flow

  1. Parse YAML template - Load template metadata and sections
  2. Set preferences - Show current mode (Interactive), confirm output file
  3. Process each section:
    • Skip if condition unmet
    • Check agent permissions (owner/editors) - note if section is restricted to specific agents
    • Draft content using section instruction
    • Present content + detailed rationale
    • IF elicit: true → MANDATORY 1-9 options format
    • Save to file if possible
  4. Continue until complete

Read the full file on GitHub · 108 lines

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.

  1. 9d ago First seen · 108 lines · 0 tokens per session scan A 5c754bff9346

Subscribe to this mod's changes

create-doc is a command published in the GitHub repository julianobarbosa/azure-finops-mcp-server (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 889 tokens. A static security scan graded it A with 0 findings. It is 97% identical to create-doc, differing in 2 lines, and is treated as a copy.