plan-forge landing-zone.instructions.md

plan-forge landing-zone.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 2,239 tokens per session, scanned A, original, MIT.

Instructions for setting up Azure Landing Zones: the shared rules and infrastructure baselines that cloud workload subscriptions must follow. They cover identity, networking, security, policies, management, tagging, and subscription organization.

In plain words
What is it for?
Use them when planning or reviewing Azure foundations for workloads. They help organize requirements for access control, network design, monitoring, security controls, policies, and resource tags.
Why use it?
They give teams a common foundation before deploying application code, reducing inconsistent or unsafe cloud setups.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

Good fit Use them when planning or reviewing Azure foundations for workloads. They help organize requirements for access control, network design, monitoring, security controls, policies, and resource tags.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/landing-zone"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/landing-zone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,239 This file is loaded in full into every session.
When invoked 2,239 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.02239 $0.02239
Opus 5.5 $0.00896 $0.00896
Sonnet 5.5 $0.00448 $0.00448
Haiku 4.5 $0.00224 $0.00224

Measured 15d ago against content hash a0950768e39c, 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 landing-zone.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 15d 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/landing-zone.instructions.md · 260 lines

How it starts

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

Azure Landing Zone Standards

Based on the Azure Landing Zone conceptual architecture. Landing Zones are the enterprise rulebook — the infrastructure baselines that every workload subscription must conform to before workload code is deployed.


Architecture Overview

                    ┌──────────────────────────────────┐
                    │         Management Baseline       │
                    │  Log Analytics · Automation ·    │
                    │  Backup · Update Mgmt · ASC       │
                    └────────────────┬─────────────────┘
                                     │ feeds
┌───────────────┐   ┌────────────────▼─────────────────┐   ┌──────────────────┐
│ Identity      │   │         Security Baseline         │   │ Network Baseline │
│ Baseline      │──►│  Defender · Sentinel · JIT ·     │◄──│ Hub-Spoke · AFW  │
│ AAD · PIM ·   │   │  SIEM · CVA · Secure Score       │   │ NSG · UDR · DNS  │
│ CA · MFA      │   └────────────────┬─────────────────┘   └──────────────────┘
└───────────────┘                    │ enforced by
                    ┌────────────────▼─────────────────┐
                    │         Policy Baseline           │
                    │  Initiatives · Deny · Audit ·    │
                    │  DeployIfNotExists · Remediation  │
                    └────────────────┬─────────────────┘
                                     │ governs
                    ┌────────────────▼─────────────────┐
                    │  Workload Subscriptions           │
                    │  (Corp · Online · Sandbox)        │
                    └──────────────────────────────────┘

Identity Baseline

// ✅ User-assigned managed identity per workload (not system-assigned)
// ✅ No service principals with client_secret in production
// ✅ PIM for all Owner/Contributor role assignments (no standing access)

// PIM role assignment via Bicep (eligible, not active)
param pimStartDateTime string = utcNow()

resource pimRoleEligibility 'Microsoft.Authorization/roleEligibilityScheduleRequests@2020-10-01' = {
  name: guid(subscription().id, principalId, contributorRoleId)
  properties: {
    principalId: principalId
    roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', contributorRoleId)
    requestType: 'AdminAssign'
    scheduleInfo: {
      startDateTime: pimStartDateTime
      expiration: { type: 'NoExpiration' }
    }
    ticketInfo: {}
  }
}

Read the full file on GitHub · 260 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. 15d ago Changed · +2 lines · +11 tokens per session a0950768e39c
  2. 1mo ago First seen · 258 lines · 2,228 tokens per session scan A 073ddadb64b1

Subscribe to this mod's changes

plan-forge landing-zone.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 4d ago), licensed MIT. It adds 2,239 tokens to every session, about $0.0090 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,649 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,257 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

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

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,159 tokens