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.
npx agentmods add instructions/srnichols/plan-forge/powershellgit clone --depth 1 https://github.com/srnichols/plan-forgeWhat 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 | $0.01387 | $0.01387 |
| Opus 5 | $0.00694 | $0.00694 |
| Sonnet 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 yesterday.
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.4
<#
.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.
- yesterday 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 (5 stars, last pushed 21d ago), licensed MIT. It adds 1,387 tokens to every session, about $0.0069 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.
Other instructions, from other repositories
dotnet-skills AGENTS.md
Instructions for managedcode/dotnet-skills, covering agents.md, purpose, solution topology, rule precedence and path and linking rules.
dotnet-skills copilot-instructions.md
Instructions for managedcode/dotnet-skills: Use AGENTS.md as the repository-wide source of truth for workflow, catalog structure, release policy, and skill maintenance rules.
Perigon.CLI copilot-instructions.md
Instructions for AterDev/Perigon.CLI, covering github copilot instructions, general guidelines, 技术栈, 项目结构与分层 and 代码风格约定.
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
maf-doctor maf-deployment.instructions.md
Always-loaded production-deployment patterns for MAF 1.3.0. Auto-applies to Program.cs, DI registration files, and infra config. Covers ManagedIdentityCredential, MaxTokens caps, secret handling, OpenTelemetry wiring, and the analyzer rules that catch regressions at write time.
maf-doctor copilot-instructions.md
Instructions for joslat/maf-doctor, covering maf 1.3.0 migration — auto-loaded constraints, maf 1.3.0 — constraints & breaking changes reference, hard constraints (never violate), fan-out / fan-in rules (silent failure risk) and key breaking changes.