testing-library

testing-library is a skill for Claude Code, Codex from dallay/agents-skills. It costs 74 tokens per session (2,424 once invoked), scanned A, original, MIT.

Testing guidance for checking web components through the actions users take, using accessibility-aware queries and realistic interactions. Testing Library is a group of tools for testing React, Vue, and browser DOM interfaces.

In plain words
What is it for?
Use it to find buttons and fields by role or label, simulate typing and clicks, test loading and asynchronous behavior, and check accessibility-related behavior.
Why use it?
It helps tests verify visible behavior instead of depending on CSS classes, internal component details, or artificial events that users cannot perform.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find buttons and fields by role or label, simulate typing and clicks, test loading and asynchronous behavior, and check accessibility-related behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dallay/agents-skills/testing-library
Install

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.

Any agent
npx skills add dallay/agents-skills --skill testing-library
Clone the repo
git clone --depth 1 https://github.com/dallay/agents-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for testing-library

README.md
[![agentmods](https://agentmods.dev/badge/skills/dallay/agents-skills/testing-library/github.svg)](https://agentmods.dev/skills/dallay/agents-skills/testing-library)
Your own site
<a href="https://agentmods.dev/skills/dallay/agents-skills/testing-library"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/testing-library/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.

agentmods 80×15 button for testing-library

Your own site · 80×15
<a href="https://agentmods.dev/skills/dallay/agents-skills/testing-library"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/testing-library.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,424 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.02424
Opus 5.5 $0.00030 $0.00970
Sonnet 5.5 $0.00015 $0.00485
Haiku 4.5 $0.00007 $0.00242

Measured 1mo ago against content hash 20304a1fb38a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-library 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.

skills/testing-library/SKILL.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to Use

  • Testing UI components with @testing-library/react, @testing-library/vue, or @testing-library/dom.
  • Choosing the right query method for elements.
  • Simulating user interactions (typing, clicking, selecting).
  • Testing async behavior (data fetching, loading states, debounced input).
  • Writing tests that enforce and verify accessibility.

Critical Patterns

  • Test User Behavior, Not Implementation: Your tests should resemble how users interact with your app. Query by role, label, and text — not by class, test ID, or component internals.
  • Query Priority: Follow this order strictly — it maps to accessibility:
    1. getByRole — accessible roles (button, textbox, heading)
    2. getByLabelText — form fields with labels
    3. getByPlaceholderText — when no label exists
    4. getByText — visible text content
    5. getByDisplayValue — current input values
    6. getByAltText — images
    7. getByTitle — title attribute
    8. getByTestId — LAST RESORT only
  • userEvent Over fireEvent: Always use @testing-library/user-event for interactions. It simulates real browser behavior (focus, keydown, keyup, input) while fireEvent dispatches a single synthetic event.
  • No Implementation Details: NEVER assert on component state, props, or internal methods. NEVER query by class name or component structure.
  • Async by Default: Use findBy queries (which return Promises) or wrap assertions in waitFor for any UI that updates asynchronously.

Code Examples

Query Priority in Practice

import { render, screen } from "@testing-library/react";
import { SignupForm } from "./SignupForm";

it("renders the signup form with accessible elements", () => {
  render(<SignupForm />);

  // BEST — getByRole with accessible name
  screen.getByRole("heading", { name: /create account/i });
  screen.getByRole("textbox", { name: /email/i });
  screen.getByRole("button", { name: /sign up/i });

  // GOOD — getByLabelText for form fields
  screen.getByLabelText(/password/i);

  // ACCEPTABLE — getByText for static content
  screen.getByText(/already have an account/i);

  // LAST RESORT — only when element has no accessible role or text
  screen.getByTestId("captcha-widget");
});

Read the full file on GitHub · 301 lines

Changes

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.

  1. 1mo ago First seen · 301 lines · 74 tokens per session scan A 20304a1fb38a

Subscribe to this mod's changes

testing-library is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 2,424 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens