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 skills/udecode/plate-template/componentsnpx skills add udecode/plate-template --skill componentsgit clone --depth 1 https://github.com/udecode/plate-templateWhat 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.00033 | $0.10704 |
| Opus 5 | $0.00016 | $0.05352 |
| Sonnet 5 | $0.00007 | $0.02141 |
| Haiku 4.5 | $0.00003 | $0.01070 |
Grade A, and why
components 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.
This is a copy
100% identical to components — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
URL: /accessibility
title: Accessibility description: Building components that are usable by everyone, including users with disabilities who rely on assistive technologies.
Accessibility (a11y) is not an optional feature—it's a fundamental requirement for modern web components. Every component must be usable by everyone, including people with visual, motor, auditory, or cognitive disabilities.
This guide is a non-exhaustive list of accessibility principles and patterns that you should follow when building components. It's not a comprehensive guide, but it should give you a sense of the types of issues you should be aware of.
If you use a linter with strong accessibility rules like Ultracite, these types of issues will likely be caught automatically, but it's still important to understand the principles.
Core Principles
- Semantic HTML First - Use native elements (
<button>,<nav>,<ul>) for built-in accessibility - Keyboard Navigation - Support Tab, Arrow keys, Home/End, Escape, Enter/Space for all interactions
- Screen Reader Support - Use ARIA attributes (
aria-label,aria-current,aria-live) for proper announcements - Visual Accessibility - Ensure focus indicators, sufficient contrast (4.5:1), and responsive text sizing
ARIA Patterns
ARIA enhances semantic HTML for assistive technologies. Key rules:
- Use semantic HTML first, ARIA only when necessary
- Don't override native semantics
- All interactive elements need keyboard access and accessible names
Common Attributes:
- Roles - Define element type (
role="button",role="navigation",role="alert") - States - Describe current state (
aria-checked,aria-expanded,aria-selected) - Properties - Provide context (
aria-label,aria-describedby,aria-controls,aria-required,aria-invalid)
Component Patterns
Complex interactive components require specific accessibility patterns. For detailed implementations, consult WAI-ARIA Authoring Practices.
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 · 1,311 lines · 33 tokens per session scan A b7e2e0c1a6ca
components is a skill published in the GitHub repository udecode/plate-template (59 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 10,704 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to components, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
autogoal
Create, verify, repair, and close durable Codex goals with measurable outcomes, evidence gates, plan templates, blocker handling, completion audits, and goal-backed workflow repair.
components
React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.
autoreview
Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.
react
React patterns with destructured props, compiler optimization, Effects, and Tailwind v4 syntax. ALWAYS use when using React.
resolve-pr-feedback
Resolve GitHub PR review feedback with source-backed triage, fixes, autogoal plan state, mandatory autoreview closeout, replies, and thread resolution.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.