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/srnichols/plan-forgeWrote 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/instructions/srnichols/plan-forge/powershell)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/powershell"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/powershell/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.
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/powershell"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/powershell.svg" alt="Reviewed on agentmods" width="80" 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.01387 | $0.01387 |
| Opus 5.5 | $0.00555 | $0.00555 |
| Sonnet 5.5 | $0.00277 | $0.00277 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
plan-forge powershell.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 20d 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Best Practices for Azure IaC
Script Structure
#Requires -Modules Az.Accounts, Az.Resources
#Requires -Version 7.6
<#
.SYNOPSIS
Short one-line description.
.DESCRIPTION
Longer description of what the script does.
.PARAMETER EnvironmentName
The target environment (dev, test, staging, prod).
.EXAMPLE
.\Deploy-Infrastructure.ps1 -EnvironmentName prod
#>
[CmdletBinding(SupportsShouldProcess)]
param (
[Parameter(Mandatory)]
[ValidateSet('dev', 'test', 'staging', 'prod')]
[string]$EnvironmentName,
[Parameter()]
[string]$Location = 'eastus'
)
Set-StrictMode -Version Latest
$ErrorActionPreference = 'Stop'
Functions
# ✅ Approved verbs, CmdletBinding, typed parameters
function New-ResourceGroupIfNotExists {
[CmdletBinding(SupportsShouldProcess)]
param (
[Parameter(Mandatory)]
[string]$Name,
[Parameter(Mandatory)]
[string]$Location,
[Parameter()]
[hashtable]$Tags = @{}
)
$existing = Get-AzResourceGroup -Name $Name -ErrorAction SilentlyContinue
if ($null -eq $existing) {
if ($PSCmdlet.ShouldProcess($Name, 'Create resource group')) {
Write-Verbose "Creating resource group '$Name' in '$Location'"
New-AzResourceGroup -Name $Name -Location $Location -Tag $Tags
}
} else {
Write-Verbose "Resource group '$Name' already exists. Skipping."
$existing
}
}
Error Handling
# ✅ Try/catch with specific error types and meaningful messages
try {
$deployment = New-AzResourceGroupDeployment @deployParams
Write-Verbose "Deployment succeeded: $($deployment.DeploymentName)"
}
catch [Microsoft.Azure.Commands.ResourceManager.Cmdlets.SdkModels.PSInvalidOperationException] {
Write-Error "Deployment validation failed: $($_.Exception.Message)"
throw
}
catch {
Write-Error "Unexpected error during deployment: $($_.Exception.Message)"
throw
}
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.
- 20d ago Changed 6cbbc6cd0b7f
- 1mo ago First seen · 193 lines · 1,387 tokens per session scan A bf715192457d
plan-forge powershell.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 8d ago), licensed MIT. It adds 1,387 tokens to every session, about $0.0055 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.
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.