Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/clubpay/ronykitnpx agentmods add skills/clubpay/ronykit/frontend-testingWrote 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/clubpay/ronykit/frontend-testing)<a href="https://agentmods.dev/skills/clubpay/ronykit/frontend-testing"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/frontend-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/clubpay/ronykit/frontend-testing"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/frontend-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 69 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Excessive Agency · line 17 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00058 | $0.01351 |
| Opus 5.5 | $0.00023 | $0.00540 |
| Sonnet 5.5 | $0.00012 | $0.00270 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
frontend-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 today.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Testing
Test what the user (and assistive tech) experiences, not implementation details. Query the DOM the way a human or screen reader does.
Close the loop yourself (do not hand back to the user)
Writing tests/code is not the finish line — a clean run is. Drive the verify-and-fix loop autonomously; never ask the user to run the app, paste errors back, or confirm a fix worked.
- Run
bash frontend/verify.sh(which runstypecheck,lint,build,test,build-storybook, UI polish static checks, and story coverage). - Read the full output, fix every error and meaningful warning, then re-run from the failed step.
- Repeat until all steps pass. Only stop to ask the user when genuinely blocked (missing secret, ambiguous product decision) — not for routine type/lint/test/build failures.
- Report completion only with fresh passing output as evidence.
When to use
- Adding tests for React components, hooks, Server Actions, or Next.js routes.
- Writing end-to-end, accessibility, or responsive layout checks with Playwright.
- Testing RonyKit TypeScript stub wrappers or WebMCP tool handlers.
- Fixing flaky or implementation-coupled frontend tests.
Levels
- Unit — pure functions, hooks, state reducers, RonyKit stub error mappers, and WebMCP tool handlers. Fast, no DOM where possible.
- Component (Vitest + Testing Library) — render a component; assert on accessible roles, states, form validation, and keyboard interaction.
- End-to-end & A11y (Playwright) — drive a real browser through critical
user journeys, WCAG scans (
@axe-core/playwright), and mobile/desktop viewport checks.
Prefer the lowest level that proves the behavior; reserve E2E for critical paths.
1. Component tests (Vitest + Testing Library)
- Query by role/label/text, never class names or internal state:
getByRole('button', { name: /delete workspace/i }),getByLabelText(/email/i). Usedata-testidonly as a last resort when no semantic role exists. - Drive interactions with
@testing-library/user-event, including keyboard flows (await user.tab(),await user.keyboard('{Enter}'),'{Escape}'). - Test the interactive states that matter (see
ux-quality):- Form validation fires on blur/submit (not first keystroke), sets
aria-invalid="true", and exposes the error viaaria-describedby. - Pending/loading state disables duplicate clicks.
- Empty vs. filtered-empty state (
"Clear filters"resets the query).
- Form validation fires on blur/submit (not first keystroke), sets
- Mock network at the boundary (MSW or typed RonyKit stub dependency injection), never by stubbing your own child components.
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.
- today Changed · +45 lines · +10 tokens per session 16b321947b7e
- 1mo ago First seen · 86 lines · 48 tokens per session scan A da5e84bf3eb8
frontend-testing is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed today), licensed BSD-3-Clause. It adds 58 tokens to every session and 1,351 once invoked, about $0.0002 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
ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
qa-orchestrator
Orchestrate multi-step change workflows (search, analyze, propose, implement, verify) with explicit evidence and gate checks.
test-runner
Run and triage Go tests with correct environment handling; produce compact, actionable failure summaries.