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 aps08/fullstack-clean-architecture --skill react_testinggit clone --depth 1 https://github.com/aps08/fullstack-clean-architectureWrote 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/aps08/fullstack-clean-architecture/react_testing)<a href="https://agentmods.dev/skills/aps08/fullstack-clean-architecture/react_testing"><img src="https://agentmods.dev/badge/skills/aps08/fullstack-clean-architecture/react_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/aps08/fullstack-clean-architecture/react_testing"><img src="https://agentmods.dev/badge/skills/aps08/fullstack-clean-architecture/react_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.00024 | $0.00921 |
| Opus 5.5 | $0.00010 | $0.00368 |
| Sonnet 5.5 | $0.00005 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
react-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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Testing Skill
Testing Tools
- Use
Vitestas the primary test runner. - Use
@testing-library/reactfor component behavior testing. - Use
Playwrightfor all End-to-End (E2E) testing.
Directory Structure
All test files are located under web/tests/ and are organized as follows:
tests/unit/: Contains unit tests testing components, hooks, features, and utils in isolation using Vitest and React Testing Library.tests/e2e/: Contains end-to-end integration tests that run in a browser using Playwright.tests/mocks/: Contains mocks for external integrations or APIs.tests/fixtures/: Contains reusable test fixtures or data.tests/test_utils.tsx: Contains common testing utilities, such as a customrenderwrapper.
Standards & Best Practices
- Test user interactions rather than implementation details.
- Ensure all tests are isolated and don't depend on global state.
- No Comments Needed: No need to add comments inside any of the test code (like
// Arrange,// Act,// Assert). Thetestoritdescription strings are enough to explain the test logic. - Code Coverage: Ensure test coverage is strictly more than 80% of the lines.
- Mocking: Use
vi.fn()for mock functions andvi.mock()for module mocks in Vitest.
Example: Unit Test (Vitest + Testing Library)
import { fireEvent, render, screen } from "@testing-library/react";
import { describe, expect, it, vi } from "vitest";
import { ArchiveCard } from "@/components/ArchiveCard";
const todo = {
id: "todo-1",
title: "Old Project Notes",
isCompleted: false,
createdAt: "2024-01-01T00:00:00Z",
updatedAt: "2024-03-01T00:00:00Z",
};
describe("ArchiveCard", () => {
it("renders the todo title", () => {
render(<ArchiveCard todo={todo} onRestore={vi.fn()} onDelete={vi.fn()} />);
expect(screen.getByText("Old Project Notes")).toBeInTheDocument();
});
it("calls onRestore with the todo id when Restore is clicked", () => {
const onRestore = vi.fn();
render(
<ArchiveCard todo={todo} onRestore={onRestore} onDelete={vi.fn()} />,
);
fireEvent.click(screen.getByRole("button"));
fireEvent.click(screen.getByText("Restore"));
expect(onRestore).toHaveBeenCalledWith("todo-1");
});
});
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 · 100 lines · 24 tokens per session scan A 8745d07e10c7
react-testing is a skill published in the GitHub repository aps08/fullstack-clean-architecture (2 stars, last pushed 18d ago), licensed Apache-2.0. It adds 24 tokens to every session and 921 once invoked, about $0.0001 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.
Other skills, from other repositories
add-test
Add tests following project test patterns.
init-verify
TEMPLATE-ONLY - verify changes against a fully running stack by instantiating the template, checking in the browser, then reverting every init artifact. Use whenever a change needs visual or runtime verification in the real app. Removed by init.sh, do not reference from skills that survive init.
testing-patterns
Testing patterns for Spring Boot - JUnit 5, Mockito, MockMvc, Testcontainers, positive and negative test cases. Use when user asks about testing, writing tests, test coverage, or test failures.
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
verify
Run full verification (backend build+test, frontend test+lint+check).