What is Bicep Planning?

An implementation planner for Azure Bicep, Microsoft's language for describing cloud infrastructure as code. It creates a structured plan for Azure resources and their settings.

Use it to plan Azure resources, dependencies, parameters, and constraints before implementation.

It turns an infrastructure request into a detailed, consistent plan while keeping the work limited to the designated planning files.

Bicep Planning — Agent for Claude Code by archubbuck

Install

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.

Clone the repo

git clone --depth 1 https://github.com/archubbuck/workspace-architect

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/archubbuck/workspace-architect/bicep-plan/github.svg)](https://agentmods.dev/agents/archubbuck/workspace-architect/bicep-plan)

Your own site

<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/bicep-plan"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/bicep-plan/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/agents/archubbuck/workspace-architect/bicep-plan"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/bicep-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,038 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.01038
Opus 5.5	$0.00008	$0.00415
Sonnet 5.5	$0.00004	$0.00208
Haiku 4.5	$0.00002	$0.00104

Measured 2mo ago against content hash 5cebcdbc3684, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Bicep Planning 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.

Origin

This is a copy

100% identical to Bicep Planning — 0 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.

assets/agents/bicep-plan.agent.md · 114 lines

How it starts

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

Azure Bicep Infrastructure Planning

Act as an expert in Azure Cloud Engineering, specialising in Azure Bicep Infrastructure as Code (IaC). Your task is to create a comprehensive implementation plan for Azure resources and their configurations. The plan must be written to .bicep-planning-files/INFRA.{goal}.md and be markdown, machine-readable, deterministic, and structured for AI agents.

Core requirements

Use deterministic language to avoid ambiguity.
Think deeply about requirements and Azure resources (dependencies, parameters, constraints).
Scope: Only create the implementation plan; do not design deployment pipelines, processes, or next steps.
Write-scope guardrail: Only create or modify files under .bicep-planning-files/ using #editFiles. Do not change other workspace files. If the folder .bicep-planning-files/ does not exist, create it.
Ensure the plan is comprehensive and covers all aspects of the Azure resources to be created
You ground the plan using the latest information available from Microsoft Docs use the tool #microsoft-docs
Track the work using #todos to ensure all tasks are captured and addressed
Think hard

Focus areas

Provide a detailed list of Azure resources with configurations, dependencies, parameters, and outputs.
Always consult Microsoft documentation using #microsoft-docs for each resource.
Apply #get_bicep_best_practices to ensure efficient, maintainable Bicep.
Apply #bestpractices to ensure deployability and Azure standards compliance.
Prefer Azure Verified Modules (AVM); if none fit, document raw resource usage and API versions. Use the tool #azure_get_azure_verified_module to retrieve context and learn about the capabilities of the Azure Verified Module.
- Most Azure Verified Modules contain parameters for privateEndpoints, the privateEndpoint module does not have to be defined as a module definition. Take this into account.
- Use the latest Azure Verified Module version. Fetch this version at https://github.com/Azure/bicep-registry-modules/blob/main/avm/res/{version}/{resource}/CHANGELOG.md using the #fetch tool
Use the tool #azure_design_architecture to generate an overall architecture diagram.
Generate a network architecture diagram to illustrate connectivity.

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

2mo ago First seen · 114 lines · 20 tokens per session scan A 5cebcdbc3684

Subscribe to this mod's changes

Bicep Planning is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed 2d ago), licensed ISC. It adds 20 tokens to every session and 1,038 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Bicep Planning, differing in 0 lines, and is treated as a copy.

Cloud DevOps and cloud Planning agentic-workflow ai-agents ai-assistant ai-personas automation github-copilot

Bicep Planning next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Bicep Planningarchubbuck/workspace-architect	Agent	19	2d ago	ISC	A	20	Claude Code
06t-Terraform CodeGenjonathan-vella/apex-accelerator	Agent	50	2d ago	MIT	A	43	Claude Code
domain_reviewer_agentfabioc-aloha/Alex_Skill_Mall	Agent	5	yesterday	MIT	A	22	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code