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.
npx agentmods add instructions/afernandes/omni.blazor/claude-mdgit clone --depth 1 https://github.com/afernandes/Omni.BlazorWrote 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/afernandes/omni.blazor/claude-md)<a href="https://agentmods.dev/instructions/afernandes/omni.blazor/claude-md"><img src="https://agentmods.dev/badge/instructions/afernandes/omni.blazor/claude-md.svg" alt="Measured on agentmods" 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 | $0.03328 | $0.03328 |
| Opus 5 | $0.01664 | $0.01664 |
| Sonnet 5 | $0.00666 | $0.00666 |
| Haiku 4.5 | $0.00333 | $0.00333 |
Grade A, and why
Omni.Blazor CLAUDE.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`docs/design-reference/` holds wireframe / mock bundles that have been used to drive past implementations (PDV, CardapioDigital, SAAS Wireframes). When the user references a "design bundle" URL of the form `https://api.a How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository layout
Three first-class projects under src/, plus a single test project:
src/Omni.Blazor/— packable Razor Class Library (Microsoft.NET.Sdk.Razor). Components may be single-file or split into.razor+.razor.cswhen complexity warrants it;docs/components.jsonis the generated catalog and API. Components live acrossComponents/{Buttons,Display,Inputs,Layout,Navigation,Overlay,Data,Forms,Marketing,Base}/. The shared SCSS bundle (Themes/omni.scss) is auto-compiled byAspNetCore.SassCompilerand served via_content/Omni.Blazor/css/omni.css.src/Omni.Blazor.Ai/— optional AI layer as a separate packable RCL (AndersonN.Omni.Blazor.Ai) referencing the base library +Microsoft.Extensions.AI.Abstractions. HoldsOmniChatClient(headless orchestrator overIChatClient) + theOmniAiConversationdrop-in. Kept out of the base package so consumers aren't forced to take the AI dependency.src/Omni.Templates/— starter/template pages RCL (Omni.Templates) + a Blazor host (Omni.Templates.Host, preview port 5305) to preview them locally.src/Forneria.Demo/— three-project showcase:.Pages(RCL with all demo pages),Forneria.Demo(Blazor Server host),Forneria.Demo.Wasm(Blazor WebAssembly host). Dual-render — both hosts reference the same.PagesRCL.src/FoodService/— POS-style consumer app:FoodService.Pages(RCL) +FoodService(Server host only). Two domain features:PdvFeature/(operator point-of-sale) andCardapioFeature/(customer-facing digital menu with 7-screen state machine).test/Omni.Blazor.Tests/— bUnit + xUnit.v3, with component, service and infrastructure coverage exceeding 2,000 tests.
Solution file: Omni.Blazor.slnx (new SDK-style solution format). Central Package Management is on — Directory.Packages.props is the single source of truth for versions; csproj files reference packages by ID only.
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.
- 4d ago First seen · 154 lines · 3,328 tokens per session scan A 064d87e288fb
Omni.Blazor CLAUDE.md is an instructions file published in the GitHub repository afernandes/Omni.Blazor (4 stars, last pushed 4d ago), licensed MIT. It adds 3,328 tokens to every session, about $0.0166 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.