plan-forge bicep.instructions.md

plan-forge bicep.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 1,728 tokens per session, scanned A, original, MIT.

A set of conventions for writing Bicep files, which describe Azure cloud infrastructure as code. It covers file organization, parameters, naming, modules, outputs, linting, and secret handling.

In plain words
What is it for?
Use it when structuring Azure infrastructure projects, defining deployment parameters, creating reusable modules, naming resources, or configuring security and lint rules.
Why use it?
It helps keep infrastructure definitions consistent, easier to review, and safer when deploying across environments.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

Good fit Use it when structuring Azure infrastructure projects, defining deployment parameters, creating reusable modules, naming resources, or configuring security and lint rules.

Compare 6 instructions from other repositories ↓
Install with agentmods
npx agentmods add instructions/srnichols/plan-forge/bicep
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/srnichols/plan-forge

Made for: GitHub Copilot.

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 plan-forge bicep.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srnichols/plan-forge/bicep/github.svg)](https://agentmods.dev/instructions/srnichols/plan-forge/bicep)
Your own site
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/bicep"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/bicep/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 plan-forge bicep.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/bicep"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/bicep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,728 This file is loaded in full into every session.
When invoked 1,728 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01728 $0.01728
Opus 5.5 $0.00691 $0.00691
Sonnet 5.5 $0.00346 $0.00346
Haiku 4.5 $0.00173 $0.00173

Measured 21d ago against content hash a7bb738aa4bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-forge bicep.instructions.md 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 21d 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.

presets/azure-iac/.github/instructions/bicep.instructions.md · 232 lines

How it starts

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

Bicep Best Practices

File Structure

infra/
├── main.bicep                  ← entry point, orchestrates modules
├── main.bicepparam             ← deployment parameters (per environment)
├── abbreviations.json          ← resource type abbreviation lookup
├── bicepconfig.json            ← linter configuration
└── modules/
    ├── networking.bicep
    ├── compute.bicep
    ├── storage.bicep
    └── security.bicep

Parameters

// ✅ Always use @description — describe what and why
@description('The environment name, used for resource naming and tagging.')
@allowed(['dev', 'test', 'staging', 'prod'])
param environmentName string

// ✅ Enforce length constraints where naming rules apply
@description('Short workload name used in resource names. 2–8 chars.')
@minLength(2)
@maxLength(8)
param workloadName string

// ✅ @secure on all secret parameters — never surfaces in logs
@description('The admin password for the database.')
@secure()
param dbAdminPassword string

// ❌ NEVER provide a non-empty default for a @secure param
@secure()
param secret string = ''      // ← only empty string is acceptable

Naming

// ✅ Use uniqueString() with a prefix for globally unique names
var storageAccountName = 'st${workloadName}${environmentName}${uniqueString(resourceGroup().id)}'

// ✅ Use template expressions for all resource names
var keyVaultName = 'kv-${workloadName}-${environmentName}-${uniqueString(resourceGroup().id)}'

// ✅ camelCase for symbolic names — never include "Name" suffix
resource keyVault 'Microsoft.KeyVault/vaults@2026-02-01' = { ... }

// ❌ NEVER hardcode resource names
resource keyVaultName 'Microsoft.KeyVault/vaults@2026-02-01' = { ... }

Resource Definitions

// ✅ Use resource properties as outputs — don't fabricate URLs
output appUrl string = appService.properties.defaultHostName

// ❌ NEVER construct URLs manually
output appUrl string = 'https://${appServiceName}.azurewebsites.net'

// ✅ Implicit dependencies via symbolic references
resource appService 'Microsoft.Web/sites@2025-03-01' = {
  properties: {
    serverFarmId: appServicePlan.id   // ← implicit dependency
  }
}

// ✅ Use existing keyword for cross-resource references
resource existingKv 'Microsoft.KeyVault/vaults@2026-02-01' existing = {
  name: keyVaultName
}

// ✅ child resources via parent property — never construct child names manually
resource secret 'Microsoft.KeyVault/vaults/secrets@2026-02-01' = {
  parent: keyVault
  name: 'mySecret'
  properties: { value: secretValue }
}

// ✅ Extract complex expressions into variables
var appServiceConfig = {
  alwaysOn: environmentName == 'prod'
  minTlsVersion: '1.2'
  ftpsState: 'Disabled'
}

Read the full file on GitHub · 232 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. 21d ago Changed a7bb738aa4bf
  2. 1mo ago First seen · 232 lines · 1,728 tokens per session scan A aa30eaa85a6a

Subscribe to this mod's changes

plan-forge bicep.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed yesterday), licensed MIT. It adds 1,728 tokens to every session, about $0.0069 per session on Opus 5.5. 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens