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-error-types)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-error-types"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-error-types/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-error-types"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-error-types.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00695 |
| Opus 5 | $0.00010 | $0.00347 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
new-error-types 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Error Types
Scaffold a custom exception hierarchy with HTTP status mapping and RFC 7807 Problem Details responses.
Required Pattern
Base Application Exception
public abstract class AppException : Exception
{
public int StatusCode { get; }
public string ErrorCode { get; }
protected AppException(string message, int statusCode, string errorCode)
: base(message)
{
StatusCode = statusCode;
ErrorCode = errorCode;
}
}
Domain Exception Types
public class NotFoundException : AppException
{
public NotFoundException(string entity, object id)
: base($"{entity} with id '{id}' was not found.", 404, "NOT_FOUND") { }
}
public class ConflictException : AppException
{
public ConflictException(string message)
: base(message, 409, "CONFLICT") { }
}
public class ValidationException : AppException
{
public IDictionary<string, string[]> Errors { get; }
public ValidationException(IDictionary<string, string[]> errors)
: base("One or more validation errors occurred.", 422, "VALIDATION_FAILED")
{
Errors = errors;
}
}
public class ForbiddenException : AppException
{
public ForbiddenException(string message = "You do not have permission to perform this action.")
: base(message, 403, "FORBIDDEN") { }
}
Global Exception Handler (Middleware)
public class GlobalExceptionHandler : IExceptionHandler
{
private readonly ILogger<GlobalExceptionHandler> _logger;
public GlobalExceptionHandler(ILogger<GlobalExceptionHandler> logger)
{
_logger = logger;
}
public async ValueTask<bool> TryHandleAsync(
HttpContext context, Exception exception, CancellationToken ct)
{
var (statusCode, errorCode, detail) = exception switch
{
AppException app => (app.StatusCode, app.ErrorCode, app.Message),
_ => (500, "INTERNAL_ERROR", "An unexpected error occurred.")
};
_logger.LogError(exception, "Unhandled exception: {ErrorCode}", errorCode);
context.Response.StatusCode = statusCode;
await context.Response.WriteAsJsonAsync(new ProblemDetails
{
Status = statusCode,
Title = errorCode,
Detail = detail,
}, ct);
return true;
}
}
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 · 117 lines · 19 tokens per session scan A d66ca6206173
new-error-types is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 695 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
api-aqa-flow-project-config-loading
Phase 0 Project Config Loading of api-aqa-flow (USER INTERACTION CONDITIONALLY REQUIRED).
api-aqa-flow-data-collection
Phase 1 Data Collection of api-aqa-flow.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
api-aqa-flow-api-spec-analysis
Phase 2 API Spec Analysis of api-aqa-flow.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).