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/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/bicep-plan)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/bicep-plan"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/bicep-plan.svg" alt="Measured on agentmods" 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.00020 | $0.01038 |
| Opus 5 | $0.00010 | $0.00519 |
| Sonnet 5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
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 7d 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.
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.
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
#todosto 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-docsfor each resource. - Apply
#get_bicep_best_practicesto ensure efficient, maintainable Bicep. - Apply
#bestpracticesto 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_moduleto 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.mdusing the#fetchtool
- Most Azure Verified Modules contain parameters for
- Use the tool
#azure_design_architectureto generate an overall architecture diagram. - Generate a network architecture diagram to illustrate connectivity.
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.
- 7d ago First seen · 114 lines · 20 tokens per session scan A 5cebcdbc3684
Bicep Planning is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,038 once invoked, about $0.0001 per session on Opus 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.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.