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/udecode/plateWrote 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/udecode/plate/sync-plate-ui)<a href="https://agentmods.dev/rules/udecode/plate/sync-plate-ui"><img src="https://agentmods.dev/badge/rules/udecode/plate/sync-plate-ui/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/udecode/plate/sync-plate-ui"><img src="https://agentmods.dev/badge/rules/udecode/plate/sync-plate-ui.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.00019 | $0.03636 |
| Opus 5.5 | $0.00008 | $0.01454 |
| Sonnet 5.5 | $0.00004 | $0.00727 |
| Haiku 4.5 | $0.00002 | $0.00364 |
Grade A, and why
sync-plate-ui 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago Changed · -6 lines · -97 tokens per session 9c9e495cde84
- 1mo ago First seen · 527 lines · 116 tokens per session scan A 6520d10fcd44
sync-plate-ui is a cursor rule published in the GitHub repository udecode/plate (16,659 stars, last pushed today), with no licence file. It adds 19 tokens to every session and 3,636 once invoked, about $0.0001 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
components
React component, styling, theme, accessibility, and RTL instructions.
single-responsibility-principle
The Single Responsibility Principle states that "A module should be responsible to one, and only one, actor." In simpler terms, a class or function should have only one reason to change.
nextjs
Keep route-specific files collocated with their route segment. Place page components, section components, and route-specific utilities inside the same directory as the route's page.tsx.
guidelines
Cursor rule "guidelines" from vucinatim/air-jam, covering tooling, conventions, refactoring, tips and notes.
typescript-best-practices-agent
This rule governs TypeScript development practices across the entire project. It should be considered whenever: (1) Planning new TypeScript features or components, (2) Modifying existing TypeScript code, (3) Reviewing or fixing TypeScript-related bugs, (4) Making architectural decisions that involve TypeScript, (5)…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.