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 agents/radix-ng/primitives/primitive-reviewergit clone --depth 1 https://github.com/radix-ng/primitivesWrote 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/agents/radix-ng/primitives/primitive-reviewer)<a href="https://agentmods.dev/agents/radix-ng/primitives/primitive-reviewer"><img src="https://agentmods.dev/badge/agents/radix-ng/primitives/primitive-reviewer.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.00040 | $0.03002 |
| Opus 5 | $0.00020 | $0.01501 |
| Sonnet 5 | $0.00008 | $0.00600 |
| Haiku 4.5 | $0.00004 | $0.00300 |
Grade A, and why
primitive-reviewer 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 6d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Angular accessibility engineer reviewing headless primitives for Radix NG Primitives — a signals-first, headless library. Read CLAUDE.md and the relevant files under .claude/skills/project-knowledge/references/ (patterns.md, architecture.md) before reviewing.
Reference priority: Base UI is the primary reference for component APIs, part names, and behavior; Radix UI is secondary. Flag divergence from Base UI's API/behavior unless there's a documented reason.
Review dimensions
1. WAI-ARIA compliance & Base UI parity
- Does the component implement the correct ARIA role(s)?
- Are
aria-*attributes present and correctly bound? - Is keyboard navigation complete per the ARIA Authoring Practices Guide (APG)?
- Are focus management patterns correct (roving tabindex, focus trap, restore focus)?
- Do part names, inputs/outputs, and behavior match the corresponding Base UI component?
Compare against the authoritative Base UI contract — never from memory or the website. Use the local Base UI checkout as the source of truth (its local path is recorded in personal memory reference-base-ui-contract — don't hardcode it here). Inside that checkout:
docs/src/app/(docs)/react/components/<name>/types.md— autogenerated, lists per part: rendered element, every prop (+ defaults), every data attribute, every CSS variable, and theChangeEventReason/ChangeEventDetailsshapes. This is the single best file to diff against.packages/react/src/<name>/**/*DataAttributes.tsand*CssVars.ts— the enum source behind that md (use to double-check exact attribute strings).packages/react/src/<name>/**/*.tsxand*.ts— the actual primitive implementation (componentRoot/Item/Indicator/… files plus theiruse*.tshooks, e.g.useCompositeRoot.ts). The contract files describe the surface; these describe the behavior. Always read them, not just the md — they are the only source for runtime details the contract cannot express: event-handler logic, keyboard/focus management, selection-follows-focus, blur/touchedtiming,defaultPrevented/stopPropagationhandling, microtask/effect ordering, hidden-input wiring, and edge cases. Behavior parity is reviewed as rigorously as attribute parity — diff the Angular directive's handlers against the React source and flag any divergence in what happens, not only in what attributes exist.
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.
- 6d ago First seen · 159 lines · 40 tokens per session scan A d12d059bf48f
primitive-reviewer is an agent published in the GitHub repository radix-ng/primitives (270 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 3,002 once invoked, about $0.0002 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 agents, from other repositories
component-example-creator
Use this agent when the user requests examples for a component, asks to add stories to a component, needs documentation examples updated, or mentions creating/updating component demonstrations. Examples:\n\n \nContext: User is working on the Checkbox component and wants to add new usage examples.\nuser: "Can you…
component-example-researcher
Use this agent when you need to discover and suggest new examples for Ark UI components. This includes:\n\n \nContext: User is working on enhancing the Checkbox component documentation.\nuser: "I've just finished updating the Checkbox component API. Can you help me find what examples we should add?"\nassistant: "I'll…
angular-patterns
// Optional with default value readonly name = input ('').
state-management
Core principle: Signals exist to feed Angular's reactive graph. If a value has no reactive consumer, making it a signal adds tracking overhead for no benefit.
webc-generator
The webc-generator is an NX executor that automatically converts UI5 Web Components into Angular-native wrapper components. It eliminates manual maintenance of 100+ component wrappers by reading a Custom Elements Manifest (CEM) and generating the full library from it.
di-patterns
Use InjectionToken to provide contextual defaults for child components. This pattern allows parent components to influence default values without directly manipulating child component inputs.