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/agents-mdgit clone --depth 1 https://github.com/afernandes/Omni.BlazorWhat 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.02541 | $0.02541 |
| Opus 5 | $0.01270 | $0.01270 |
| Sonnet 5 | $0.00508 | $0.00508 |
| Haiku 4.5 | $0.00254 | $0.00254 |
Grade A, and why
Omni.Blazor AGENTS.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 2d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Omni.Blazor
Entry point for AI coding agents (Claude Code, Cursor, Copilot, v0, …) — whether you are generating UI with this library or contributing to it. Humans: see CLAUDE.md (architecture deep-dive) and CONTRIBUTING.md.
What this is
Omni.Blazor — a packable Razor Class Library for .NET 10. 210 components (authoritative count + full API: docs/components.json)
across AI, Buttons, Data, Display, Forms, Inputs, Layout, Marketing, Navigation and
Overlay. One SCSS bundle, isolated feature ES modules, all theming via CSS custom properties.
| NuGet package id | AndersonN.Omni.Blazor |
| Localization packages | AndersonN.Omni.Localization, .Json, .Po |
| Namespace / assembly | Omni.Blazor |
| Static assets | _content/Omni.Blazor/css/omni.css, lazily imported JS modules |
| CSS class prefix | omni- |
| Design-token prefix | --omni- |
| JS interop | scoped typed services + isolated ES modules |
Machine-readable surface — read these first
Do not browse component source files to learn the API. Read the generated artifacts:
llms.txt— curated index: every component with a one-line description and a source link, grouped by category. Start here.llms-full.txt— full dump: every component's parameters, events, slots, enum values and the theme tokens.docs/components.json— the same data, structured (per component:parameters/events/slotswithtype,enumValues,default,required,summary). Generated — never hand-edit.
These three are produced by one reflection-based generator. Regenerate after any
change to the public component surface (new component, new/renamed [Parameter],
new enum, edited XML doc):
dotnet run --project tools/Omni.Blazor.ManifestGen
pwsh ./tools/generate-localization-resources.ps1 # after changing OmniTexts
Agent Skill (building applications)
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.
- 2d ago First seen · 195 lines · 2,541 tokens per session scan A 1ccfa047ff23
Omni.Blazor AGENTS.md is an instructions file published in the GitHub repository afernandes/Omni.Blazor (4 stars, last pushed 5d ago), licensed MIT. It adds 2,541 tokens to every session, about $0.0127 per session on Opus 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).
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.