ag-ui-a2ui-integration skillA
ag-ui-a2ui-integration is agent-read markdown (skill) from modem-dev/ossrules: Use when adding A2UI rendering to any AG-UI-supported framework or custom AG-UI application, scaffolding an AG-UI app that should render A2UI, adapting an AG-UI integration to emit A2UI surfaces, or wiring the AG-UI A2UI middleware/toolkit with a compatible renderer..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# AG-UI + A2UI Integration Skill ## Overview Use this skill to add A2UI rendering to an AG-UI application. Treat AG-UI as the transport and agent integration layer, `@ag-ui/a2ui-middleware` as the server-side bridge that detects and paints A2UI operations, and A2UI as the UI payload format that the client renderer displays. This is a developer-facing skill artifact. It is meant to be loaded by coding agents and used against a real app or repo, not published as a docs page. ## When to Use - Adding A2UI rendering to an existing AG-UI app. - Creating an AG-UI quickstart that should display A2UI surfaces. - Connecting any AG-UI-supported framework or custom AG-UI agent to an A2UI-capable frontend. - Adding or extending an A2UI component catalog. - Debugging why an A2UI surface does not render or why a user action does not flow back to the agent. ## When NOT to Use - For AG-UI protocol event semantics only, use the AG-UI protocol skill or protocol docs. - For A2UI renderer internals outside an AG-UI app, use the A2UI renderer docs or renderer-specific skills. - For generic CopilotKit frontend work without A2UI, use CopilotKit-specific setup and React skills. …
Read the whole file at its exact version.
How to install
mdr add modem-dev/ossrules/ag-ui-a2ui-integration@v1.1.0mdr add modem-dev/ossrules/ag-ui-a2ui-integration@sha256:6a39ebd30e506af8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_mks2h7ugjppj7ol7)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6131 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
modem-dev/ossrules · 52 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mks2h7ugjppj7ol7 GET https://markdownregistry.com/api/v1/resolve?ref=modem-dev/ossrules/ag-ui-a2ui-integration GET https://markdownregistry.com/api/v1/blob/6a39ebd30e506af8612e0f5d1a49462a2bbb5c5d58d2bbbce8392fd1e501de97
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.