Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/srnichols/plan-forgenpx agentmods add instructions/srnichols/plan-forge/daprWrote 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/dapr)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/dapr"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/dapr/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/dapr"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/dapr.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.04975 | $0.04975 |
| Opus 5.5 | $0.01990 | $0.01990 |
| Sonnet 5.5 | $0.00995 | $0.00995 |
| Haiku 4.5 | $0.00498 | $0.00498 |
Grade A, and why
plan-forge dapr.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 15d 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 — 672 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Dapr Patterns
Standard: Dapr v1.18+ with Aspire 13.6 / Docker Compose Packages:
Dapr.AspNetCore,Dapr.Client,Dapr.Workflow1.18.x Cross-ref:messaging.instructions.mdcovers pub/sub message schemas and CloudEvents in detail
Sidecar Architecture
Non-Negotiable Rules
- NEVER call external services directly — always go through the Dapr sidecar
- NEVER hardcode Dapr HTTP/gRPC ports — use
DAPR_HTTP_ENDPOINT/DAPR_GRPC_ENDPOINTenv vars - ALWAYS scope components to the services that need them
- ALWAYS use the typed
DaprClient— never raw HTTP tolocalhost:3500
DaprClient Registration
// Program.cs — register DaprClient with DI
var builder = WebApplication.CreateBuilder(args);
// Standard registration
builder.Services.AddDaprClient();
// NativeAOT-compatible registration (source-generated JSON)
builder.Services.AddDaprClient(clientBuilder =>
{
clientBuilder.UseJsonSerializationOptions(new JsonSerializerOptions
{
TypeInfoResolver = AppJsonContext.Default,
PropertyNamingPolicy = JsonNamingPolicy.CamelCase
});
});
var app = builder.Build();
app.MapSubscribeHandler(); // Required for pub/sub subscriptions
Docker Compose Sidecar Pattern
# Each service gets its own Dapr sidecar container
my-service:
build: ./MyService
environment:
- DAPR_HTTP_ENDPOINT=http://my-service-sidecar:3500
- DAPR_GRPC_ENDPOINT=http://my-service-sidecar:50001
my-service-sidecar:
image: daprio/daprd:1.18.4
command:
- ./daprd
- --app-id=my-service
- --app-port=8080
- --dapr-http-port=3500
- --dapr-grpc-port=50001
- --resources-path=/components
- --log-level=info
volumes:
- ./dapr/components:/components
network_mode: service:my-service # Share network namespace
# Placement service (required for actors/workflows)
dapr-placement:
image: daprio/dapr:1.18.4
command: ["./placement", "--port", "50006"]
State Management
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.
- 15d ago Changed · +7 tokens per session 6cbd7f80f423
- 1mo ago First seen · 672 lines · 4,968 tokens per session scan A ad7623919d62
plan-forge dapr.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 4d ago), licensed MIT. It adds 4,975 tokens to every session, about $0.0199 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.