testing

A collection of patterns for testing software, including unit tests for individual pieces, integration tests for connected parts, and TDD, a method of writing tests before the code they check.

In plain words
What is it for?
Use it to write or improve tests, set up test infrastructure, create mocks and test data, check coverage, and investigate failing tests.
Why use it?
It helps catch regressions and makes tests easier to organize, maintain, and diagnose when they fail.

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/macromania/agentop/testing
Any agent
npx skills add macromania/agentop --skill testing
Clone the repo
git clone --depth 1 https://github.com/macromania/agentop

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,310 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.00062 $0.03310
Opus 5 $0.00031 $0.01655
Sonnet 5 $0.00012 $0.00662
Haiku 4.5 $0.00006 $0.00331

Measured yesterday against content hash 1f50642c2023, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.github/skills/testing/SKILL.md · 525 lines

How it starts

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

Testing Patterns

Testing strategies and patterns for building reliable, maintainable code with comprehensive test coverage.

When to Use This Skill

  • Writing new tests
  • Setting up test infrastructure
  • Debugging failing tests
  • Improving test coverage
  • Following TDD methodology
  • Writing integration tests

Test Structure

AAA Pattern (Arrange, Act, Assert)

import { describe, it, expect, beforeEach } from 'vitest';

describe('TaskService', () => {
  let service: TaskService;
  let mockDb: MockDatabase;

  beforeEach(() => {
    // Shared setup
    mockDb = createMockDatabase();
    service = new TaskService(mockDb);
  });

  it('should create a task with default priority', async () => {
    // Arrange - set up test data
    const outcomeId = 'outcome-123';
    const title = 'Implement feature';
    
    // Act - execute the code under test
    const task = await service.createTask({ outcomeId, title });
    
    // Assert - verify the results
    expect(task.id).toBeDefined();
    expect(task.title).toBe(title);
    expect(task.priority).toBe(3);  // default
    expect(task.status).toBe('pending');
  });

  it('should throw when outcome does not exist', async () => {
    // Arrange
    const invalidOutcomeId = 'nonexistent';
    
    // Act & Assert
    await expect(
      service.createTask({ outcomeId: invalidOutcomeId, title: 'Test' })
    ).rejects.toThrow('Outcome not found');
  });
});

Test Naming Convention

// Format: should [expected behavior] when [condition]

describe('SessionManager', () => {
  // Good names - clear and specific
  it('should start session when outcome has no blockers', () => {});
  it('should throw SessionActiveError when session already running', () => {});
  it('should emit progress events during task execution', () => {});
  it('should cleanup resources when session is stopped', () => {});
  
  // Bad names - vague or implementation-focused
  it('test start', () => {});  // What does it test?
  it('calls processTask', () => {});  // Testing implementation, not behavior
  it('works correctly', () => {});  // What is "correct"?
});

Read the full file on GitHub · 525 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 · 525 lines · 62 tokens per session scan A 1f50642c2023

Subscribe to this mod's changes

testing is a skill published in the GitHub repository macromania/agentop (10 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 3,310 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-31.