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/authgit 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.02552 | $0.02552 |
| Opus 5 | $0.01276 | $0.01276 |
| Sonnet 5 | $0.00510 | $0.00510 |
| Haiku 4.5 | $0.00255 | $0.00255 |
Grade A, and why
plan-forge auth.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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Authentication & Authorization
Middleware Pipeline Order
// ⚠️ ORDER MATTERS — incorrect ordering breaks auth silently
var app = builder.Build();
app.UseHttpsRedirection();
app.UseCors();
app.UseAuthentication(); // 1. WHO are you? (parses token → ClaimsPrincipal)
app.UseAuthorization(); // 2. CAN you do this? (checks policies/roles)
app.UseRateLimiter();
app.MapControllers();
JWT / OpenID Connect Setup
OIDC with Identity Provider (Entra ID / Auth0 / Keycloak)
builder.Services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
.AddJwtBearer(options =>
{
options.Authority = builder.Configuration["Auth:Authority"];
options.Audience = builder.Configuration["Auth:Audience"];
options.RequireHttpsMetadata = !builder.Environment.IsDevelopment();
options.TokenValidationParameters = new TokenValidationParameters
{
ValidateIssuer = true,
ValidateAudience = true,
ValidateLifetime = true,
ValidateIssuerSigningKey = true,
ClockSkew = TimeSpan.FromMinutes(1), // Default 5 min is too generous
NameClaimType = "name",
RoleClaimType = "roles",
};
// Map external claims to internal user context
options.Events = new JwtBearerEvents
{
OnTokenValidated = context =>
{
var tenantId = context.Principal?.FindFirst("tenant_id")?.Value;
if (!string.IsNullOrEmpty(tenantId))
{
var identity = (ClaimsIdentity)context.Principal!.Identity!;
identity.AddClaim(new Claim("tenant_id", tenantId));
}
return Task.CompletedTask;
},
};
});
Configuration (appsettings.json)
{
"Auth": {
"Authority": "https://login.microsoftonline.com/{tenant-id}/v2.0",
"Audience": "api://{client-id}"
}
}
Policy-Based Authorization
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 · 375 lines · 2,552 tokens per session scan A 6685a6d2fa63
plan-forge auth.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 21d ago), licensed MIT. It adds 2,552 tokens to every session, about $0.0128 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.