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/commands/srnichols/plan-forge/new-middleware)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-middleware"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-middleware.svg" alt="Measured on agentmods" 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.00022 | $0.00640 |
| Opus 5 | $0.00011 | $0.00320 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
new-middleware 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 today.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Middleware
Scaffold an ASP.NET Core middleware component for the HTTP request pipeline.
Required Pattern
Convention-Based Middleware
public class {Name}Middleware(
RequestDelegate next,
ILogger<{Name}Middleware> logger)
{
public async Task InvokeAsync(HttpContext context)
{
// Pre-processing (before the next middleware)
logger.LogDebug("{Name}Middleware executing for {Path}", context.Request.Path);
try
{
await next(context);
}
finally
{
// Post-processing (after the response)
}
}
}
// Extension method for clean registration
public static class {Name}MiddlewareExtensions
{
public static IApplicationBuilder Use{Name}(this IApplicationBuilder builder)
=> builder.UseMiddleware<{Name}Middleware>();
}
Scoped-Service Middleware (IMiddleware)
// Use when the middleware needs scoped services
public class {Name}Middleware(ILogger<{Name}Middleware> logger) : IMiddleware
{
public async Task InvokeAsync(HttpContext context, RequestDelegate next)
{
// Access scoped services directly via constructor injection
await next(context);
}
}
// Must register in DI
builder.Services.AddScoped<{Name}Middleware>();
Registration Order (Program.cs)
// Order matters! Follow this sequence:
app.UseExceptionHandler(); // 1. Error handling (outermost)
app.UseCorrelationId(); // 2. Correlation ID
app.UseRequestLogging(); // 3. Request logging
app.UseAuthentication(); // 4. Authentication
app.UseAuthorization(); // 5. Authorization
app.UseRateLimiting(); // 6. Rate limiting
app.Use{Name}(); // 7. Your custom middleware
Common Middleware Types
| Type | Purpose | Example |
|---|---|---|
| Correlation ID | Attach trace ID to every request | Read/generate X-Correlation-Id header |
| Tenant Resolution | Extract tenant from token/header | Set ITenantContext.TenantId |
| Request Logging | Log method, path, status, duration | Structured log with Serilog |
| Exception Handling | Map exceptions to ProblemDetails | Global try/catch with RFC 9457 |
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.
- today First seen · 93 lines · 22 tokens per session scan A a08dbd1c2aec
new-middleware is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 640 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
nxt-api-route
Generates a Next.js App Router API route handler (route.ts) with proper TypeScript types, request validation, and error handling. Auto-detects auth patterns from the project.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.