What is extract-infrastructure?

A command that examines Azure infrastructure and creates a Docker Compose setup for local development. Azure is Microsoft's cloud platform, while Docker Compose describes several local containers and how they run together.

It helps inspect existing Azure resources and generate a local stack using emulators for Azure services.

It helps developers reproduce parts of a cloud environment on their own machines. This can make local testing possible without relying on the original Azure deployment.

extract-infrastructure — Command for Claude Code by JosiahSiegel

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/JosiahSiegel/claude-plugin-marketplace

agentmods

npx agentmods add commands/josiahsiegel/claude-plugin-marketplace/extract-infrastructure

Made for: Claude Code.

Or install azure-to-docker-master, the plugin that ships this one along with the rest of its 3 skills, 2 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/extract-infrastructure/github.svg)](https://agentmods.dev/commands/josiahsiegel/claude-plugin-marketplace/extract-infrastructure)

Your own site

<a href="https://agentmods.dev/commands/josiahsiegel/claude-plugin-marketplace/extract-infrastructure"><img src="https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/extract-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/josiahsiegel/claude-plugin-marketplace/extract-infrastructure"><img src="https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/extract-infrastructure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,198 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.04198
Opus 5	$0.00005	$0.02099
Sonnet 5	$0.00002	$0.00840
Haiku 4.5	$0.00001	$0.00420

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

Security

Grade A, and why

extract-infrastructure scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

test: ["CMD", "curl", "-f", "http://localhost:PORT/health"]

plugins/azure-to-docker-master/commands/extract-infrastructure.md · 625 lines

How it starts

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

🚨 CRITICAL GUIDELINES

Windows File Path Requirements

MANDATORY: Always Use Backslashes on Windows for File Paths

When using Edit or Write tools on Windows, you MUST use backslashes (\) in file paths, NOT forward slashes (/).

Examples:

❌ WRONG: D:/repos/project/file.tsx
✅ CORRECT: D:\repos\project\file.tsx

This applies to:

Edit tool file_path parameter
Write tool file_path parameter
All file operations on Windows systems

Documentation Guidelines

NEVER create new documentation files unless explicitly requested by the user.

Priority: Update existing README.md files rather than creating new documentation
Repository cleanliness: Keep repository root clean - only README.md unless user requests otherwise
Style: Documentation should be concise, direct, and professional - avoid AI-generated tone
User preference: Only create additional .md files when user specifically asks for documentation

Extract Azure Infrastructure to Docker Compose

Purpose

Analyze existing Azure infrastructure and generate a complete Docker Compose stack with Azure service emulators for local development.

Prerequisites

Required tools:

Azure CLI (az) installed and configured
Docker Desktop 4.40+ with Compose v2.42+
Sufficient local resources (minimum 8GB RAM for full Azure stack)

Azure access:

Authenticated with az login
Appropriate RBAC permissions to read resources
Access to target resource group

Step 1: Authenticate with Azure

# Login to Azure
az login

# List available subscriptions
az account list --output table

# Set target subscription
az account set --subscription "subscription-name-or-id"

# Verify current subscription
az account show

Step 2: Extract Azure Resources

List Resources in Resource Group

# List all resources in resource group
az resource list \
  --resource-group <resource-group-name> \
  --output table

# Get detailed JSON output for analysis
az resource list \
  --resource-group <resource-group-name> \
  --output json > azure-resources.json

Read the full file on GitHub · 625 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.

11d ago First seen · 625 lines · 11 tokens per session scan A c97cf4396fa0

Subscribe to this mod's changes

extract-infrastructure is a command published in the GitHub repository JosiahSiegel/claude-plugin-marketplace (54 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 4,198 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Cloud Containers DevOps and cloud

create-docker-mcp-tunnel

Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).

anthropics/claude-plugins-official · 26 tokens

k8s-manifest

Generate production-ready Kubernetes manifests for the current application.

rohitg00/awesome-claude-code-toolkit · 0 tokens

cisco-isovalent-platform-setup

Install the Isovalent platform on Kubernetes (Cilium CNI, Hubble observability, Tetragon eBPF runtime security) in either OSS or Enterprise edition. Renders Helm values and install/upgrade scripts; this is the platform install prerequisite for the Splunk Observability + Splunk Platform integration done by…

chambear2809/splunk-cisco-skills · 0 tokens

extract-infrastructure