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/multi-environmentgit 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.01067 | $0.01067 |
| Opus 5 | $0.00534 | $0.00534 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
plan-forge multi-environment.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 2d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Environment Configuration (.NET)
Environment Hierarchy
| Environment | Purpose | Config File | Detection |
|---|---|---|---|
Development |
Local dev with hot reload | appsettings.Development.json |
ASPNETCORE_ENVIRONMENT |
Staging |
Pre-production validation | appsettings.Staging.json |
ASPNETCORE_ENVIRONMENT |
Production |
Live traffic | appsettings.Production.json |
ASPNETCORE_ENVIRONMENT |
Configuration Loading Order
appsettings.json ← Base (all environments)
appsettings.{Environment}.json ← Environment-specific overrides
Environment variables ← Infrastructure overrides (highest priority)
User secrets (dev only) ← Local developer secrets
Rules
- NEVER put secrets in
appsettings.json— use User Secrets (dev) or Key Vault (prod) - NEVER hardcode environment-specific URLs — use config per environment
- ALWAYS have a base
appsettings.jsonwith sensible defaults - ALWAYS use
IOptions<T>/IOptionsSnapshot<T>for typed config - Environment variables override JSON settings (12-factor app)
Per-Environment Settings
// appsettings.Development.json
{
"ConnectionStrings": {
"Database": "Host=localhost;Port=5432;Database=contoso_dev;Username=dev;Password=devpass"
},
"Logging": { "LogLevel": { "Default": "Debug" } },
"Cors": { "Origins": ["http://localhost:3000", "http://localhost:5173"] }
}
// appsettings.Staging.json
{
"ConnectionStrings": {
"Database": "Host=staging-db;Port=5432;Database=contoso_staging"
},
"Logging": { "LogLevel": { "Default": "Information" } },
"Cors": { "Origins": ["https://staging.contoso.com"] }
}
// appsettings.Production.json
{
"ConnectionStrings": {
"Database": "" // Injected via environment variable or Key Vault
},
"Logging": { "LogLevel": { "Default": "Warning" } },
"Cors": { "Origins": ["https://contoso.com", "https://www.contoso.com"] }
}
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.
- 2d ago First seen · 138 lines · 1,067 tokens per session scan A fee4a40940c5
plan-forge multi-environment.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,067 tokens to every session, about $0.0053 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.