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/blazor-fluent-ui)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/blazor-fluent-ui"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/blazor-fluent-ui/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/blazor-fluent-ui"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/blazor-fluent-ui.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.03144 | $0.03144 |
| Opus 5.5 | $0.01258 | $0.01258 |
| Sonnet 5.5 | $0.00629 | $0.00629 |
| Haiku 4.5 | $0.00314 | $0.00314 |
Grade A, and why
plan-forge blazor-fluent-ui.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 24d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blazor + Fluent UI Patterns
Stack assumption: Blazor Server (interactive server rendering) on .NET 10 with
Microsoft.FluentUI.AspNetCore.Components4.14.x. Adapt selectively for Blazor WebAssembly or Blazor United.
The Layering Rule (Non-Negotiable)
A .razor component is Presentation. It does ONE thing: render UI and dispatch events. Everything else is delegated.
.razor / .razor.cs (Presentation)
↓ inject
Application service interface (IClientService, IBillingService, …)
↓ implementation
Repository / DbContext (Data Access)
Forbidden in .razor / .razor.cs
| Anti-pattern | Why | Fix |
|---|---|---|
@inject MyDbContext Db |
Components become untestable; couples UI to ORM | Inject a service interface; service owns the DbContext |
Inline LINQ over DbSet<T> |
Same — embeds query logic in presentation | Move query into the service; component calls service.GetXAsync(ct) |
Business rules (if (entry.Hours > 8) entry.IsOvertime = true) |
Logic that must hold across surfaces (UI, API, jobs) cannot live in one of them | Move to a domain method or service |
HttpClient instantiated with new |
No DI, no testability, leaks sockets | Use IHttpClientFactory or a typed client registered in DI |
Task.Run(() => …) to "make it async" |
Wastes a thread; doesn't make the call truly async | If the underlying API is sync, leave it sync; otherwise call the real async API |
.Result / .Wait() / .GetAwaiter().GetResult() in lifecycle methods |
Deadlocks Blazor Server's render loop | await properly inside OnInitializedAsync / OnParametersSetAsync |
Catch Exception and silently swallow |
Hides defects; user sees a half-rendered page with no signal | Catch specific types, log structured, surface a MessageBar or Toast |
Component Anatomy (Code-Behind Preferred)
For anything beyond a trivial display component, separate markup from code-behind. This makes the component reviewable and unit-testable with bUnit.
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.
- 24d ago Changed · +4 tokens per session 582d767a2093
- 1mo ago First seen · 313 lines · 3,140 tokens per session scan A 4690f394b173
plan-forge blazor-fluent-ui.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 3,144 tokens to every session, about $0.0126 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.