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 iwritec0de/app-dev --skill js-testinggit clone --depth 1 https://github.com/iwritec0de/app-devWrote 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/iwritec0de/app-dev/js-testing)<a href="https://agentmods.dev/skills/iwritec0de/app-dev/js-testing"><img src="https://agentmods.dev/badge/skills/iwritec0de/app-dev/js-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/iwritec0de/app-dev/js-testing"><img src="https://agentmods.dev/badge/skills/iwritec0de/app-dev/js-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.00100 | $0.05952 |
| Opus 5.5 | $0.00040 | $0.02381 |
| Sonnet 5.5 | $0.00020 | $0.01190 |
| Haiku 4.5 | $0.00010 | $0.00595 |
Grade A, and why
js-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 2mo 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 — 921 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JS Testing Skill — Vitest + React Testing Library for Next.js
Critical Rules
- Vitest is the test runner. Do not use Jest. All configuration, mocking, and assertions use the Vitest API (
vi.fn(),vi.mock(),vi.spyOn(), etc.). - React Testing Library (RTL) for component tests. Query elements the way a user would find them — by role, label, text, or placeholder. Never reach for
getByTestIdunless no semantic query is possible. - Test user behavior, not implementation. Assert what the user sees and can interact with. Do not assert on component state, refs, internal variables, or hook return values directly (except when using
renderHook). - Never test React internals. Do not mock
useState,useEffect,useRef, or any React built-in. If you need to control what a hook returns, extract the logic into a custom hook and test it withrenderHook. - Use MSW for API mocking. Mock at the network layer with Mock Service Worker, not by stubbing
fetchoraxiosdirectly. This gives realistic request/response cycles and catches serialization issues. - Prefer
userEventoverfireEvent.userEventsimulates real browser behavior (focus, blur, keystrokes).fireEventdispatches synthetic DOM events and should only be used for eventsuserEventdoes not support. - Every test file must be self-contained. Shared setup belongs in
vitest.setup.tsor a dedicated test utility file, not scattered across tests via implicit globals.
Component Testing
Basic Render Test
// components/greeting.tsx
export function Greeting({ name }: { name: string }) {
return <h1>Hello, {name}!</h1>;
}
// components/greeting.test.tsx
import { render, screen } from "@testing-library/react";
import { describe, it, expect } from "vitest";
import { Greeting } from "./greeting";
describe("Greeting", () => {
it("renders the user name", () => {
render(<Greeting name="Kelley" />);
expect(
screen.getByRole("heading", { name: /hello, kelley/i })
).toBeInTheDocument();
});
});
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.
- 2mo ago First seen · 921 lines · 100 tokens per session scan A ea0548d50d21
js-testing is a skill published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 7mo ago), licensed MIT. It adds 100 tokens to every session and 5,952 once invoked, about $0.0004 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.
js-testing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| js-testingiwritec0de/app-dev | Skill | 3 | 7mo ago | MIT | A | 100 | Claude Code |
| r-testthatposit-dev/skills | Skill | 567 | 5d ago | MIT | A | 77 | Claude Code |
| r-package-developmentposit-dev/skills | Skill | 567 | 5d ago | MIT | A | 41 | Claude Code |
| cloudflare-workers-testingsecondsky/claude-skills | Skill | 250 | 17d ago | MIT | A | 57 | Claude Code |
| bun-test-lifecyclesecondsky/claude-skills | Skill | 250 | 17d ago | MIT | A | 27 | Claude Code |
| bun-test-mockingsecondsky/claude-skills | Skill | 250 | 17d ago | MIT | A | 25 | Claude Code |
| bun-test-basicssecondsky/claude-skills | Skill | 250 | 17d ago | MIT | A | 28 | Claude Code |