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/clubpay/ronykit/frontend-testingnpx skills add clubpay/ronykit --skill frontend-testinggit clone --depth 1 https://github.com/clubpay/ronykitWrote 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.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 | $0.00048 | $0.00797 |
| Opus 5 | $0.00024 | $0.00398 |
| Sonnet 5 | $0.00010 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00080 |
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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Testing
Test what the user experiences, not implementation details. Query the DOM the way a user (or assistive tech) 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
pnpm typecheck,pnpm lint,pnpm build,pnpm test(andpnpm build-storybookwhen present) for the target app. - 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, or Next.js routes.
- Writing end-to-end flows with Playwright.
- Fixing flaky or implementation-coupled frontend tests.
Levels
- Unit — pure functions, hooks, utilities. Fast, no DOM where possible.
- Component — render a component with Testing Library; assert on visible output and behavior.
- End-to-end — Playwright drives a real browser through whole user flows.
Prefer the lowest level that proves the behavior; reserve E2E for critical paths.
Component tests (Vitest + Testing Library)
- Query by role/label/text, not test IDs or class names:
getByRole('button', { name: /save/i }). Usedata-testidonly as a last resort. - Drive interactions with
@testing-library/user-event, not rawfireEvent. - Assert on what the user sees (text, roles, ARIA state), never on component internals or props.
- Use
findBy*/waitForfor async UI instead of fixed timeouts. - Mock network at the boundary (e.g. MSW), not by stubbing your own components.
test('submits the form', async () => {
const user = userEvent.setup()
render(<LoginForm onSubmit={onSubmit} />)
await user.type(screen.getByLabelText(/email/i), '[email protected]')
await user.click(screen.getByRole('button', { name: /sign in/i }))
expect(onSubmit).toHaveBeenCalledWith({ email: '[email protected]' })
})
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.
- 4d 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 3d ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 797 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 skills, from other repositories
sql-database-support
Guides classifying, gap-analyzing, and scaffolding support for a new SQL database in pREST (wire-compatible variants like TimescaleDB or new dialects). Use when adding database support, creating integration/ /, DIFFERENCES.md, adapters/ , per-DB docker-compose or GitHub workflows, or planning where config/app wiring…
prest-integration-tests
Guides writing and reviewing pREST Docker/network integration tests under integration/ so each request is human-readable via step comments or table-driven descriptions. Use when adding or editing integration//test.go, HTTP controller E2E coverage, make test-integration, test-integration-postgres…
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
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).