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/messaging)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/messaging"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/messaging/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/messaging"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/messaging.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.01477 | $0.01477 |
| Opus 5.5 | $0.00591 | $0.00591 |
| Sonnet 5.5 | $0.00295 | $0.00295 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
plan-forge messaging.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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Messaging & Pub/Sub Patterns
Messaging Strategy
Dapr Pub/Sub (Recommended for Service Mesh)
// Publishing events
public class OrderService(DaprClient daprClient)
{
public async Task PlaceOrderAsync(Order order, CancellationToken ct = default)
{
await _repository.SaveAsync(order, ct);
await daprClient.PublishEventAsync(
"pubsub", // component name
"order-placed", // topic
new OrderPlacedEvent(order.Id, order.TenantId, DateTimeOffset.UtcNow),
ct);
}
}
// Subscribing to events
[ApiController]
public class OrderEventsController : ControllerBase
{
[Topic("pubsub", "order-placed")]
[HttpPost("/events/order-placed")]
public async Task<IActionResult> HandleOrderPlaced(
OrderPlacedEvent evt, [FromServices] IOrderProcessor processor, CancellationToken ct)
{
await processor.ProcessAsync(evt, ct);
return Ok();
}
}
NATS JetStream (Direct)
// Publishing
await js.PublishAsync("orders.placed", new OrderPlacedEvent { ... }, cancellationToken: ct);
// Subscribing (durable consumer)
var consumer = await js.CreateOrUpdateConsumerAsync("orders", new ConsumerConfig
{
DurableName = "order-processor",
FilterSubject = "orders.placed",
AckPolicy = ConsumerConfigAckPolicy.Explicit,
});
MassTransit (RabbitMQ / Azure Service Bus)
// Program.cs
builder.Services.AddMassTransit(x =>
{
x.AddConsumer<OrderPlacedConsumer>();
x.UsingRabbitMq((context, cfg) =>
{
cfg.Host(builder.Configuration.GetConnectionString("RabbitMQ"));
cfg.ConfigureEndpoints(context);
});
});
// Consumer
public class OrderPlacedConsumer : IConsumer<OrderPlacedEvent>
{
public async Task Consume(ConsumeContext<OrderPlacedEvent> context)
{
var evt = context.Message;
// Process event
}
}
Event Schema (CloudEvents)
// Always use typed events — never raw strings
public record OrderPlacedEvent(
Guid OrderId,
string TenantId,
DateTimeOffset OccurredAt);
// Include tenant_id in ALL events for multi-tenant routing
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 · 217 lines · 1,477 tokens per session scan A 4f6d880bafd3
plan-forge messaging.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 8d ago), licensed MIT. It adds 1,477 tokens to every session, about $0.0059 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.