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/iliaal/whetstone/testing-reactnpx skills add iliaal/whetstone --skill testing-reactgit clone --depth 1 https://github.com/iliaal/whetstoneWhat 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.00057 | $0.01015 |
| Opus 5 | $0.00028 | $0.00508 |
| Sonnet 5 | $0.00011 | $0.00203 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
testing-react 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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Classification
| Type | Tool | Target | File pattern |
|---|---|---|---|
| Unit | Vitest | Pure functions, utilities, services | Co-located *.test.ts |
| Component | Vitest + RTL | React components | Co-located *.test.tsx |
| Hook | Vitest + RTL | Custom hooks | Co-located *.test.ts |
| E2E | Playwright | User flows, critical paths | Separate e2e/ directory |
Default to component tests for React components. Unit tests for pure functions and service classes. See e2e-testing for Playwright patterns.
Setup
Vitest config: environment: 'jsdom', globals: true, setupFiles pointing to a file that imports @testing-library/jest-dom/vitest. Use @vitejs/plugin-react and mirror path aliases from tsconfig.json.
Critical Rules
- Query priority:
getByRole>getByLabelText>getByPlaceholderText>getByText>getByTestId. Usedata-testidonly when no accessible query works. - Mock boundaries: Mock API services, navigation, and external providers. Render child components and UI libraries real for integration confidence.
- One behavior per test with AAA structure. Name tests
should <behavior> when <condition>. - Async: Use
findBy*for async elements,waitForafter state-triggering actions,vi.useFakeTimers()for debounce/timer logic. - User events: Prefer
userEventoverfireEventfor realistic interactions. - Cleanup:
vi.clearAllMocks()inbeforeEach. Recreate test state per test instead of sharing mutable variables. - Incremental workflow: When testing a directory, process one file at a time (simplest first). Run and verify each before proceeding.
- Tests expose bugs, not the reverse: If a test uncovers broken or buggy behavior, highlight the issue and propose a fix to the source code. Never adjust the test to match incorrect behavior.
Component Test
import { render, screen, waitFor } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
vi.mock('@/api/client');
describe('UserForm', () => {
beforeEach(() => { vi.clearAllMocks(); });
it('should submit valid form data', async () => {
const onSubmit = vi.fn();
render(<UserForm onSubmit={onSubmit} />);
await userEvent.type(screen.getByLabelText(/email/i), '[email protected]');
await userEvent.click(screen.getByRole('button', { name: /submit/i }));
await waitFor(() => {
expect(onSubmit).toHaveBeenCalledWith(
expect.objectContaining({ email: '[email protected]' }),
);
});
});
});
What ships with it
2 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.
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.
- 2d ago First seen · 106 lines · 57 tokens per session scan A 050174b4c5a3
testing-react is a skill published in the GitHub repository iliaal/whetstone (32 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 1,015 once invoked, about $0.0003 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.