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,228 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

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.

agentmods
npx agentmods add instructions/srnichols/plan-forge/landing-zone
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.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,228 This file is loaded in full into every session.
When invoked 2,228 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02228 $0.02228
Opus 5 $0.01114 $0.01114
Sonnet 5 $0.00446 $0.00446
Haiku 4.5 $0.00223 $0.00223

Measured 3d ago against content hash 073ddadb64b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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 · 258 lines

How it starts

The opening of the file, as written. The whole thing — 258 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)
resource pimRoleEligibility 'Microsoft.Authorization/roleEligibilityScheduleRequests@2022-04-01-preview' = {
  name: guid(subscription().id, principalId, contributorRoleId)
  properties: {
    principalId: principalId
    roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', contributorRoleId)
    requestType: 'AdminAssign'
    scheduleInfo: {
      startDateTime: utcNow()
      expiration: { type: 'NoExpiration' }
    }
    ticketInfo: {}
  }
}

Read the full file on GitHub · 258 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. 3d 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 (5 stars, last pushed today), licensed MIT. It adds 2,228 tokens to every session, about $0.0111 per session on Opus 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.