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.
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/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/rules/ag-ui-protocol/ag-ui/project-rules)<a href="https://agentmods.dev/rules/ag-ui-protocol/ag-ui/project-rules"><img src="https://agentmods.dev/badge/rules/ag-ui-protocol/ag-ui/project-rules/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/rules/ag-ui-protocol/ag-ui/project-rules"><img src="https://agentmods.dev/badge/rules/ag-ui-protocol/ag-ui/project-rules.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.00082 | $0.00082 |
| Opus 5.5 | $0.00033 | $0.00033 |
| Sonnet 5.5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
project-rules 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 1mo 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.
What it actually says
Project Overview
This monorepo project utilizes:
- Nx for build system orchestration
- PNPM for package management
- Vitest for unit testing
Test files are located in __tests__ directories alongside their corresponding implementation files.
Note: To run tests, navigate to the specific package directory and execute pnpm run test
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.
- 1mo ago First seen · 18 lines · 82 tokens per session scan A fd86a327454e
project-rules is a cursor rule published in the GitHub repository ag-ui-protocol/ag-ui (16,604 stars, last pushed today), licensed MIT. It adds 82 tokens to every session, about $0.0003 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-30.
Other cursor rules, from other repositories
spec-workflow
SDD specification protocol: risk-based specmode classification, required sections per mode, plan approval gate, and artifact directory conventions.
pi-en
PI Cognitive AI. Trigger: $pi/coding/dev/code/architecture/API/refactor/debug/bug/error/exception/crash/timeout/performance/optimization/test/compile/git/release/verify/review/CR/product/requirements/ops/growth/design/team/support, or deep/2+ failures/looping/stuck/giving-up/retry/nevermind.
tools
(none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.
testing
Guide for writing pytest unit and integration tests.
development-phase
A development rule that favors clear, well-structured new code and considers compatibility only when it costs nothing.
env-access
Supporting rule — STRICT block on .env access (read AND write). Only .env.example is accessible. Backs rule 1 (write allowlist) with a stricter dual-key bypass.