testing-standards

testing-standards is a skill for Claude Code, Codex from shwilliamson/automatasaurus. It costs 29 tokens per session (1,409 once invoked), scanned A, original, MIT.

Guidance for choosing what to test and writing tests that check software behaviour, including unit, integration, and end-to-end tests.

In plain words
What is it for?
Use it when writing tests, reviewing test coverage, or setting up a testing process.
Why use it?
It helps catch bugs, protect existing behaviour during code changes, and avoid spending time testing unimportant details.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/shwilliamson/automatasaurus/testing-standards
Any agent
npx skills add shwilliamson/automatasaurus --skill testing-standards
Clone the repo
git clone --depth 1 https://github.com/shwilliamson/automatasaurus

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/testing-standards.svg)](https://agentmods.dev/skills/shwilliamson/automatasaurus/testing-standards)
Your own site
<a href="https://agentmods.dev/skills/shwilliamson/automatasaurus/testing-standards"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/testing-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,409 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00029 $0.01409
Opus 5 $0.00015 $0.00705
Sonnet 5 $0.00006 $0.00282
Haiku 4.5 $0.00003 $0.00141

Measured 5d ago against content hash 649663726c8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing-standards 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 5d 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.

template/skills/testing-standards/SKILL.md · 245 lines

How it starts

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

Testing Standards

Guidelines for writing effective tests that catch bugs, enable refactoring, and document behavior.

Testing Pyramid

Prefer more tests at the bottom, fewer at the top:

        /  E2E  \        Few, slow, high confidence
       /----------\
      / Integration \    Some, medium speed
     /----------------\
    /    Unit Tests    \  Many, fast, focused

What to Test

Always Test

  • Business logic and calculations
  • Edge cases and boundary conditions
  • Error handling paths
  • Public API contracts
  • Security-sensitive code
  • Complex conditionals

Usually Skip

  • Simple getters/setters
  • Framework code (React renders, Express routing)
  • Third-party library internals
  • Private implementation details
  • Logging statements

Unit Tests

Structure: Arrange-Act-Assert

test('calculates total with discount', () => {
  // Arrange
  const cart = new Cart([{ price: 100 }, { price: 50 }]);
  const discount = 0.1;

  // Act
  const total = cart.calculateTotal(discount);

  // Assert
  expect(total).toBe(135);
});

Naming Convention

test('[unit] [action] [expected result] [condition]')

Examples:

  • test('User.validate rejects empty email')
  • test('calculateTax returns 0 for tax-exempt items')
  • test('login redirects to dashboard on success')

Keep Tests Focused

// Bad: Testing multiple behaviors
test('user registration', () => {
  expect(validate(user)).toBe(true);
  expect(hash(password)).toMatch(/^\$2b\$/);
  expect(sendEmail).toHaveBeenCalled();
  expect(db.save).toHaveBeenCalled();
});

// Good: One behavior per test
test('validates user email format', () => { ... });
test('hashes password with bcrypt', () => { ... });
test('sends welcome email after registration', () => { ... });
test('persists user to database', () => { ... });

Integration Tests

Test how components work together:

describe('User Registration Flow', () => {
  test('creates user and sends welcome email', async () => {
    const response = await request(app)
      .post('/api/users')
      .send({ email: '[email protected]', password: 'secure123' });

    expect(response.status).toBe(201);
    expect(await User.findByEmail('[email protected]')).toBeTruthy();
    expect(emailService.sent).toContainEqual(
      expect.objectContaining({ to: '[email protected]' })
    );
  });
});

Read the full file on GitHub · 245 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. 5d ago First seen · 245 lines · 29 tokens per session scan A 649663726c8d

Subscribe to this mod's changes

testing-standards is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,409 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

testing

Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.

iOfficeAI/AionUi · 55 tokens

testing-patterns

Testing patterns and principles. Unit, integration, mocking strategies.

vudovn/ag-kit · 16 tokens

testing

Writing or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.

latitude-dev/latitude-llm · 41 tokens

detect-flaky-tests

Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…

agent-substrate/substrate · 102 tokens

test-pyramid

Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need E2E coverage, and where coverage is duplicated. Use when the user asks about test pyramid, test rebalancing, "should this…

kubernetes-sigs/agent-sandbox · 104 tokens

designing-tests

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

CloudAI-X/claude-workflow-v2 · 48 tokens