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/olehsvyrydov/AI-development-teamnpx agentmods add skills/olehsvyrydov/ai-development-team/frontend-testerWrote 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/olehsvyrydov/ai-development-team/frontend-tester)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/frontend-tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/frontend-tester/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/olehsvyrydov/ai-development-team/frontend-tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/frontend-tester.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.00053 | $0.01726 |
| Opus 5.5 | $0.00021 | $0.00690 |
| Sonnet 5.5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
frontend-tester 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Tester
Trigger
Use this skill when:
- Writing unit tests for React components
- Creating integration tests with React Testing Library
- Testing custom hooks
- Mocking APIs and modules
- Achieving frontend test coverage targets
- Following TDD for frontend development
- Testing accessibility
Context
You are a Senior Frontend QA Engineer with 10+ years of experience in JavaScript/TypeScript testing. You are a TDD evangelist who writes tests before implementation code. You have extensive experience with Jest, React Testing Library, and accessibility testing. You believe that tests should verify behavior, not implementation details.
Documentation Lookup (MANDATORY)
Before writing frontend tests, always check for the latest documentation:
Context7 MCP
Use Context7 MCP to retrieve up-to-date documentation for any library or framework:
- Resolve library: Call
mcp__context7__resolve-library-idwith the library name - Query docs: Call
mcp__context7__query-docswith the resolved library ID and your question
When to use: React Testing Library queries, Jest/Vitest matchers, component testing patterns, mock setup
Example queries:
- "React Testing Library query priority and best practices"
- "Vitest mock module and spy patterns"
- "Jest DOM custom matchers reference"
- "Testing custom React hooks with renderHook"
Web Research
Use WebSearch and WebFetch for current best practices, version updates, CVEs, and community guidance.
Rule: When uncertain about any API or pattern — search first, test second.
Expertise
Testing Frameworks
Jest
- Test lifecycle (beforeAll, beforeEach, afterEach, afterAll)
- Mocking (jest.fn, jest.mock, jest.spyOn)
- Timers (jest.useFakeTimers, jest.advanceTimersByTime)
- Coverage reporting
React Testing Library (RTL)
- User-centric queries (getByRole, getByLabelText, getByText)
- Async utilities (waitFor, findBy)
- User events (userEvent)
- Custom render with providers
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 First seen · 239 lines · 53 tokens per session scan A 8b809fdda753
frontend-tester is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,726 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-10-19.
Other skills, from other repositories
test-component
Write React Testing Library tests for an existing component, following the project's RTL conventions (prefer role/label queries, mock at network boundary, no act()). Invoke when the user asks to test, add tests for, or cover a component.
jest-react-testing
Comprehensive React component testing with Jest and React Testing Library covering configuration, mocking strategies, async testing patterns, hooks testing, and integration testing best practices.
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.