testing-patterns

testing-patterns is a skill for Claude Code, Codex from seandkendall/kiro-config. It costs 40 tokens per session (674 once invoked), scanned A, original, Apache-2.0.

A collection of examples for testing Python functions and React components. It includes pytest and moto for Python, Vitest and React Testing Library for React, coverage commands, and Playwright for browser-based tests.

In plain words
What is it for?
Use it to write unit tests, React component tests, AWS Lambda tests, coverage checks, and browser end-to-end tests.
Why use it?
It provides starting points for checking both server-side behavior and user-interface behavior without designing each test setup from scratch. It also shows how to test code that interacts with AWS services in a local mock.

Skill for Claude CodeCodex

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

Good fit Use it to write unit tests, React component tests, AWS Lambda tests, coverage checks, and browser end-to-end tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/seandkendall/kiro-config/testing-patterns
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 seandkendall/kiro-config --skill testing-patterns
Clone the repo
git clone --depth 1 https://github.com/seandkendall/kiro-config

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/seandkendall/kiro-config/testing-patterns"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 674 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.00040 $0.00674
Opus 5.5 $0.00016 $0.00270
Sonnet 5.5 $0.00008 $0.00135
Haiku 4.5 $0.00004 $0.00067

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

Security

Grade A, and why

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

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-patterns/SKILL.md · 73 lines

How it starts

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

Testing Patterns

Python Lambda Test (pytest + moto)

import pytest
from moto import mock_aws
import boto3, os

@pytest.fixture
def dynamodb_table():
    with mock_aws():
        os.environ["TABLE_NAME"] = "test-table"
        client = boto3.client("dynamodb", region_name="us-east-1")
        client.create_table(
            TableName="test-table",
            KeySchema=[{"AttributeName": "PK", "KeyType": "HASH"}, {"AttributeName": "SK", "KeyType": "RANGE"}],
            AttributeDefinitions=[{"AttributeName": "PK", "AttributeType": "S"}, {"AttributeName": "SK", "AttributeType": "S"}],
            BillingMode="PAY_PER_REQUEST",
        )
        yield client

def test_handler_success(dynamodb_table):
    from my_function import lambda_handler
    result = lambda_handler({"body": '{"name": "test"}'}, MockContext())
    assert result["statusCode"] == 200

def test_handler_validation_error(dynamodb_table):
    from my_function import lambda_handler
    result = lambda_handler({"body": '{}'}, MockContext())
    assert result["statusCode"] == 400

React Component Test (Vitest + RTL)

import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
import { axe } from 'jest-axe';

test('submits form with valid data', async () => {
  const onSubmit = vi.fn();
  render(<InvoiceForm onSubmit={onSubmit} />);
  await userEvent.type(screen.getByLabelText('Amount'), '100');
  await userEvent.click(screen.getByRole('button', { name: 'Submit' }));
  expect(onSubmit).toHaveBeenCalledWith(expect.objectContaining({ amount: 100 }));
});

test('has no accessibility violations', async () => {
  const { container } = render(<InvoiceForm />);
  expect(await axe(container)).toHaveNoViolations();
});

Coverage Commands

  • Python: pytest --cov --cov-report=term-missing --cov-fail-under=90
  • React: npx vitest --coverage
  • Playwright: npx playwright test with playwright-coverage or monocart-coverage-reports
  • Target: 100%. Never settle below 90%.

Read the full file on GitHub · 73 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. yesterday First seen · 73 lines · 40 tokens per session scan A 43426c694b03

Subscribe to this mod's changes

testing-patterns is a skill published in the GitHub repository seandkendall/kiro-config (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 674 once invoked, about $0.0002 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-10-27.

Related

Other skills, from other repositories