AG-UI is an event-based protocol that lets AI agent backends communicate with user-facing applications. It standardizes agent events and inputs while supporting transports such as server-sent events, WebSockets, and webhooks. The catalogue add-ons help developers build integrations and applications around the protocol.
Borrowing it
Nothing to install: this file belongs to ag-ui-protocol/ag-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ag-ui-protocol/ag-ui/main/.github/skills/agui-dotnet-sdk-docs/SKILL.mdgit clone --depth 1 https://github.com/ag-ui-protocol/ag-uiWrote 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/skills/ag-ui-protocol/ag-ui/agui-dotnet-sdk-docs)<a href="https://agentmods.dev/skills/ag-ui-protocol/ag-ui/agui-dotnet-sdk-docs"><img src="https://agentmods.dev/badge/skills/ag-ui-protocol/ag-ui/agui-dotnet-sdk-docs.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.1 | $0.00155 | $0.01457 |
| Opus 5 | $0.00077 | $0.00728 |
| Sonnet 5 | $0.00031 | $0.00291 |
| Haiku 4.5 | $0.00015 | $0.00146 |
Grade A, and why
agui-dotnet-sdk-docs 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 7d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AG-UI .NET SDK — Docs Site Authoring
The published docs at docs.ag-ui.com are a Mintlify project rooted at
docs/. The .NET SDK section is a sibling of the TypeScript and Python
sections. Pages live as .mdx files and are wired into navigation through
docs/docs.json. Get the location or the nav wrong and the page renders nowhere
or breaks the build.
Where .NET docs live
docs/
docs.json # nav + global anchors (single source of truth)
sdk/dotnet/
abstractions/{overview,types,events,multimodal-inputs}.mdx # AGUI.Abstractions
client/{overview,chat-client,transport}.mdx # AGUI.Client
hosting/{overview,endpoints,extensibility}.mdx # AGUI.Hosting.AspNetCore
sdk/js/**, sdk/python/** # sibling sections — the style reference
The .NET nav group in docs.json mirrors the js and python
groups: subgroups named after the packages
(AGUI.Abstractions, AGUI.Client, AGUI.Hosting.AspNetCore) each listing
page paths without the .mdx extension. A global anchor .NET SDK
points at sdk/dotnet/abstractions/overview. (The anchor icon and its CSS
treatment are already set up; this skill is about adding and editing pages, not
the anchor.)
Page conventions (mirror the JS pages)
Study the JS sibling for any page you add — docs/sdk/js/core/overview.mdx,
docs/sdk/js/client/*.mdx — and keep the .NET page parallel in shape.
- Frontmatter:
title(Title Case, e.g."Overview","AGUIChatClient") anddescription(one line). Seedocs/sdk/dotnet/abstractions/overview.mdx. - H1 names the package or type (
# AGUI.Abstractions,# AGUIChatClient), matching the JS H1 convention (# @ag-ui/core). - Install fence uses
dotnet add package AGUI.*(JS usesnpm install @ag-ui/*). - Cross-links are root-absolute:
/sdk/dotnet/abstractions/types#runagentinput. - Mintlify components are in scope (
<Note>,<Card>,<Tip>, etc.) — use the same ones the surrounding .NET/JS pages use; don't introduce new patterns.
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.
- 7d ago First seen · 120 lines · 155 tokens per session scan A f12af6a9b241
agui-dotnet-sdk-docs is a skill published in the GitHub repository ag-ui-protocol/ag-ui (15,743 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session and 1,457 once invoked, about $0.0008 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-30.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.