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 skills add udecode/plate-playground-template --skill testinggit clone --depth 1 https://github.com/udecode/plate-playground-templateWrote 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/skills/udecode/plate-playground-template/testing)<a href="https://agentmods.dev/skills/udecode/plate-playground-template/testing"><img src="https://agentmods.dev/badge/skills/udecode/plate-playground-template/testing/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/skills/udecode/plate-playground-template/testing"><img src="https://agentmods.dev/badge/skills/udecode/plate-playground-template/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00005 | $0.00345 |
| Opus 5.5 | $0.00002 | $0.00138 |
| Sonnet 5.5 | $0.00001 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
testing 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- testing — 100% identical, 0 lines differ
What it actually says
Testing Goal
Keep tests in three buckets only:
- Pure unit tests for deterministic logic.
- Thin component or hook contract tests for real app behavior.
- Golden input or output tests when serialized output is the contract.
Hard constraints:
- Prefer Bun for the fast local loop.
- Keep the default suite fast.
- No browser or e2e coverage unless the app behavior truly needs it.
- Coverage is a hotspot tool, not a vanity score.
Core Rules
- Assert public behavior, not implementation detail.
- Keep tests next to the code they cover with
*.spec.ts[x]. - Keep helpers local. Do not import one spec from another.
- Prefer explicit assertions over snapshots.
- Delete skipped, commented, or placeholder tests instead of babysitting them.
Seam Selection
- Use plain function tests for pure logic.
- Use rendered React tests for hooks, components, rerender behavior, and DOM behavior.
- Use browser checks only when the contract is actually browser-specific.
Fixtures And Assertions
- Keep fixtures small.
- Use plain objects for simple state.
- Use
it.eachfor small behavior matrices. - In Bun + Testing Library, prefer render-returned queries over
screen. - Use direct style-property assertions instead of
toHaveStyle. - Use snapshots only when serialized output is the contract and inline assertions would be worse.
Quick Reference
- Keep tests fast and local.
- Start with the smallest seam that proves the behavior.
- Prefer explicit assertions.
- Browser checks are for real UI behavior, not lazy coverage.
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 · 53 lines · 5 tokens per session scan A 3afb99842911
testing is a skill published in the GitHub repository udecode/plate-playground-template (241 stars, last pushed 3d ago), licensed MIT. It adds 5 tokens to every session and 345 once invoked, about $0.0000 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 skills, from other repositories
testing
Skill "testing" from udecode/plate-template, covering testing goal, core rules, seam selection, fixtures and assertions and quick reference.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.