javascript-testing-patterns

javascript-testing-patterns is a skill for Claude Code, Codex from frontal-labs/mcp-server. It costs 63 tokens per session (3,539 once invoked), scanned B, a copy of javascript-testing-patterns, Apache-2.0.

A guide to testing JavaScript and TypeScript programs with tools such as Jest, Vitest, and Testing Library. It covers unit tests for small pieces of code, integration tests for connected parts, and end-to-end tests for complete user flows.

In plain words
What is it for?
Use it to set up test infrastructure, test functions, APIs, and user interfaces, or add tests to continuous integration. It also covers TDD, a practice of writing a failing test before writing the code that makes it pass.
Why use it?
It helps replace ad-hoc test setups with a consistent approach for checking code and preventing regressions. It also explains mocks and fixtures, which stand in for outside services or prepared test data.

Skill for Claude CodeCodex

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { logger } from "../utils/logger";.

Good fit Use it to set up test infrastructure, test functions, APIs, and user interfaces, or add tests to continuous integration. It also covers TDD, a practice of writing a failing test before writing the code that makes it pass.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/frontal-labs/mcp-server
agentmods
npx agentmods add skills/frontal-labs/mcp-server/javascript-testing-patterns

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 javascript-testing-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/frontal-labs/mcp-server/javascript-testing-patterns/github.svg)](https://agentmods.dev/skills/frontal-labs/mcp-server/javascript-testing-patterns)
Your own site
<a href="https://agentmods.dev/skills/frontal-labs/mcp-server/javascript-testing-patterns"><img src="https://agentmods.dev/badge/skills/frontal-labs/mcp-server/javascript-testing-patterns/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 javascript-testing-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/frontal-labs/mcp-server/javascript-testing-patterns"><img src="https://agentmods.dev/badge/skills/frontal-labs/mcp-server/javascript-testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,539 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00063 $0.03539
Opus 5.5 $0.00025 $0.01416
Sonnet 5.5 $0.00013 $0.00708
Haiku 4.5 $0.00006 $0.00354

Measured yesterday against content hash d99e1d7344ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

javascript-testing-patterns scanned grade B with 1 finding 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 yesterday.

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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

const response = await fetch("https://api.example.com/users", { method: "POST",
Origin

This is a copy

100% identical to javascript-testing-patterns — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/javascript-testing-patterns/SKILL.md · 538 lines

How it starts

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

JavaScript Testing Patterns

Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.

When to Use This Skill

  • Setting up test infrastructure for new projects
  • Writing unit tests for functions and classes
  • Creating integration tests for APIs and services
  • Implementing end-to-end tests for user flows
  • Mocking external dependencies and APIs
  • Testing React, Vue, or other frontend components
  • Implementing test-driven development (TDD)
  • Setting up continuous testing in CI/CD pipelines

Testing Frameworks

Jest - Full-Featured Testing Framework

Setup:

// jest.config.ts
import type { Config } from "jest";

const config: Config = {
  preset: "ts-jest",
  testEnvironment: "node",
  roots: ["<rootDir>/src"],
  testMatch: ["**/__tests__/**/*.ts", "**/?(*.)+(spec|test).ts"],
  collectCoverageFrom: [
    "src/**/*.ts",
    "!src/**/*.d.ts",
    "!src/**/*.interface.ts",
  ],
  coverageThreshold: {
    global: {
      branches: 80,
      functions: 80,
      lines: 80,
      statements: 80,
    },
  },
  setupFilesAfterEnv: ["<rootDir>/src/test/setup.ts"],
};

export default config;

Vitest - Fast, Vite-Native Testing

Setup:

// vitest.config.ts
import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    globals: true,
    environment: "node",
    coverage: {
      provider: "v8",
      reporter: ["text", "json", "html"],
      exclude: ["**/*.d.ts", "**/*.config.ts", "**/dist/**"],
    },
    setupFiles: ["./src/test/setup.ts"],
  },
});

Unit Testing Patterns

Pattern 1: Testing Pure Functions

// utils/calculator.ts
export function add(a: number, b: number): number {
  return a + b;
}

export function divide(a: number, b: number): number {
  if (b === 0) {
    throw new Error("Division by zero");
  }
  return a / b;
}

// utils/calculator.test.ts
import { describe, it, expect } from "vitest";
import { add, divide } from "./calculator";

describe("Calculator", () => {
  describe("add", () => {
    it("should add two positive numbers", () => {
      expect(add(2, 3)).toBe(5);
    });

    it("should add negative numbers", () => {
      expect(add(-2, -3)).toBe(-5);
    });

    it("should handle zero", () => {
      expect(add(0, 5)).toBe(5);
      expect(add(5, 0)).toBe(5);
    });
  });

  describe("divide", () => {
    it("should divide two numbers", () => {
      expect(divide(10, 2)).toBe(5);
    });

    it("should handle decimal results", () => {
      expect(divide(5, 2)).toBe(2.5);
    });

    it("should throw error when dividing by zero", () => {
      expect(() => divide(10, 0)).toThrow("Division by zero");
    });
  });
});

Read the full file on GitHub · 538 lines

Files

What ships with it

1 file 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.

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. yesterday First seen · 538 lines · 63 tokens per session scan B d99e1d7344ca

Subscribe to this mod's changes

javascript-testing-patterns is a skill published in the GitHub repository frontal-labs/mcp-server (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 3,539 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (sends data to an external url). It is 100% identical to javascript-testing-patterns, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

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.

affaan-m/ECC · 43 tokens

testing

Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.

evanca/flutter-ai-rules · 33 tokens

testing-patterns

Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.

yonatangross/orchestkit · 59 tokens

knowledge-engineering-quality-and-delivery-unit-integration-and-shared-test-harnesses

A testing guide for the CLI and web interfaces, covering unit, integration, end-to-end, and real-process test setup with shared fixtures and cleanup.

echoVic/blade-code · 184 tokens

continuous-testing

Continuous test-driven development loop — after every code change, builds the project, starts the server, and runs Unit Tests, Integration Tests, and System Tests. Applies on top of microprofile-server skill. Use during development when you want full verification after each change. Triggers on "continuous testing"…

AdamBien/airails · 84 tokens

pn-testing-strategy

Testing strategy and pyramid. Unit/integration/E2E ratio, Vitest vs Playwright vs MSW, contract testing, and test-environment setup. Use when defining or reviewing a project's testing approach.

perniemann/pnCore · 46 tokens