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 dvasyliev/ai-dev-tools-getting-started --skill frontend-testinggit clone --depth 1 https://github.com/dvasyliev/ai-dev-tools-getting-startedWrote 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/dvasyliev/ai-dev-tools-getting-started/frontend-testing)<a href="https://agentmods.dev/skills/dvasyliev/ai-dev-tools-getting-started/frontend-testing"><img src="https://agentmods.dev/badge/skills/dvasyliev/ai-dev-tools-getting-started/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/dvasyliev/ai-dev-tools-getting-started/frontend-testing"><img src="https://agentmods.dev/badge/skills/dvasyliev/ai-dev-tools-getting-started/frontend-testing.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.00050 | $0.02616 |
| Opus 5.5 | $0.00020 | $0.01046 |
| Sonnet 5.5 | $0.00010 | $0.00523 |
| Haiku 4.5 | $0.00005 | $0.00262 |
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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/component-test.template.tsx 12 KB
- assets/hook-test.template.ts 6.6 KB runs code
- assets/utility-test.template.ts 5.0 KB runs code
- references/async-testing.md 8.3 KB
- references/checklist.md 6.1 KB
- references/common-patterns.md 11 KB
- references/domain-components.md 15 KB
- references/mocking.md 15 KB
- references/workflow.md 7.8 KB
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 · 338 lines · 50 tokens per session scan A ac0b53966ba6
frontend-testing is a skill published in the GitHub repository dvasyliev/ai-dev-tools-getting-started (21 stars, last pushed 6mo ago), with no licence file. It adds 50 tokens to every session and 2,616 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
react-testing-library
Covers React Testing Library for component and hook tests — queries, async, userEvent, providers, brittle-test anti-patterns. Use for any test rendering a component or hook.
front-vitest
Depth for Vitest tests of front- React 19 SPAs when DOM, RTL, TanStack Query hooks, or TanStack Router route-tree tests are needed. USE WHEN: adding jsdom or testing-library, writing tsx render or renderHook tests, testing createMemoryHistory plus RouterProvider, Suspense UI, or React 19 act fixtures. DO NOT USE WHEN…
component-creation
Step-by-step workflow for creating accessible, tested UI components. Use when the user asks to create a new UI component.
nestjs-testing-expert
Writes NestJS Vitest tests — testing modules, provider mocks, service/controller specs, Supertest e2e. Use for any test touching a NestJS service, controller, guard, or endpoint.
refactor-code
Refactors code safely behind tests without changing behavior. Use when asked to refactor, clean up, simplify, reduce complexity, or pay down technical debt in specific code.
execution-debugging
Scoped debugging methodology for when a test or build fails during execution/stabilization. Use to diagnose the failing check without scope-creeping — read the full error, reproduce in isolation, hypothesize before changing, localize, fix the root cause not the symptom, and guard with a regression test.