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/instructions/srnichols/plan-forge/api-patterns)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/api-patterns"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/api-patterns/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/instructions/srnichols/plan-forge/api-patterns"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/api-patterns.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.02049 | $0.02049 |
| Opus 5.5 | $0.00820 | $0.00820 |
| Sonnet 5.5 | $0.00410 | $0.00410 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
plan-forge api-patterns.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 1mo 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET API Patterns
REST Conventions
Controller Structure
[ApiController]
[Route("api/[controller]")]
[Produces("application/json")]
public class ProducersController(IProducerService service) : ControllerBase
{
[HttpGet]
public async Task<ActionResult<PagedResult<ProducerDto>>> GetAll(
[FromQuery] int page = 1, [FromQuery] int pageSize = 25, CancellationToken ct = default)
{
var result = await service.GetPagedAsync(page, pageSize, ct);
return Ok(result);
}
[HttpGet("{id:guid}")]
public async Task<ActionResult<ProducerDto>> GetById(Guid id, CancellationToken ct = default)
{
var producer = await service.GetByIdAsync(id, ct);
return producer is null ? NotFound() : Ok(producer);
}
[HttpPost]
public async Task<ActionResult<ProducerDto>> Create(
[FromBody] CreateProducerRequest request, CancellationToken ct = default)
{
var created = await service.CreateAsync(request, ct);
return CreatedAtAction(nameof(GetById), new { id = created.Id }, created);
}
[HttpPut("{id:guid}")]
public async Task<IActionResult> Update(
Guid id, [FromBody] UpdateProducerRequest request, CancellationToken ct = default)
{
await service.UpdateAsync(id, request, ct);
return NoContent();
}
[HttpDelete("{id:guid}")]
public async Task<IActionResult> Delete(Guid id, CancellationToken ct = default)
{
await service.DeleteAsync(id, ct);
return NoContent();
}
}
Error Responses (ProblemDetails — RFC 9457)
// Automatic via app.UseExceptionHandler + ProblemDetails
builder.Services.AddProblemDetails(options =>
{
options.CustomizeProblemDetails = ctx =>
{
ctx.ProblemDetails.Extensions["traceId"] = ctx.HttpContext.TraceIdentifier;
};
});
// Manual ProblemDetails
return Problem(
title: "Producer not found",
detail: $"No producer with ID {id} exists",
statusCode: StatusCodes.Status404NotFound,
type: "https://tools.ietf.org/html/rfc9110#section-15.5.5");
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.
- 1mo ago First seen · 249 lines · 2,049 tokens per session scan A 92703380a421
plan-forge api-patterns.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 8d ago), licensed MIT. It adds 2,049 tokens to every session, about $0.0082 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.