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/observabilitygit 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.01237 | $0.01237 |
| Opus 5 | $0.00619 | $0.00619 |
| Sonnet 5 | $0.00247 | $0.00247 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
plan-forge observability.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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Observability Patterns
Structured Logging
Source-Generated Logging (Recommended)
public partial class OrderService
{
[LoggerMessage(Level = LogLevel.Information, Message = "Order {OrderId} placed for tenant {TenantId}")]
partial void LogOrderPlaced(string orderId, string tenantId);
[LoggerMessage(Level = LogLevel.Error, Message = "Order processing failed for {OrderId}")]
partial void LogOrderFailed(string orderId, Exception ex);
}
Logging Guidelines
// ✅ Structured parameters (not string interpolation)
logger.LogInformation("Processing order {OrderId} for tenant {TenantId}", orderId, tenantId);
// ❌ String interpolation (not queryable)
logger.LogInformation($"Processing order {orderId} for tenant {tenantId}");
OpenTelemetry Setup
Registration
builder.Services.AddOpenTelemetry()
.WithTracing(tracing => tracing
.AddSource("MyApp")
.AddAspNetCoreInstrumentation()
.AddHttpClientInstrumentation()
.AddNpgsql()
.AddOtlpExporter())
.WithMetrics(metrics => metrics
.AddMeter("MyApp")
.AddAspNetCoreInstrumentation()
.AddHttpClientInstrumentation()
.AddOtlpExporter());
Custom Traces
private static readonly ActivitySource Activity = new("MyApp.Orders");
public async Task<Order> PlaceOrderAsync(OrderRequest request, CancellationToken ct)
{
using var activity = Activity.StartActivity("PlaceOrder");
activity?.SetTag("tenant.id", request.TenantId);
activity?.SetTag("order.type", request.Type);
var order = await _repository.SaveAsync(request, ct);
activity?.SetTag("order.id", order.Id);
return order;
}
Custom Metrics
private static readonly Meter Meter = new("MyApp.Orders");
private static readonly Counter<long> OrdersPlaced = Meter.CreateCounter<long>("orders.placed");
private static readonly Histogram<double> OrderProcessingTime = Meter.CreateHistogram<double>("orders.processing_ms");
public async Task ProcessAsync(Order order, CancellationToken ct)
{
var sw = Stopwatch.StartNew();
// ... process
OrdersPlaced.Add(1, new KeyValuePair<string, object?>("tenant", order.TenantId));
OrderProcessingTime.Record(sw.Elapsed.TotalMilliseconds);
}
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 · 172 lines · 1,237 tokens per session scan A a94105791865
plan-forge observability.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,237 tokens to every session, about $0.0062 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.