test-automation

test-automation is a skill for Claude Code from MonumentalSystems/Atlas-Agent-Teams. It costs 10 tokens per session (1,070 once invoked), scanned A, original, MIT.

A reference for planning and maintaining automated tests. It explains how to divide tests between individual code units, connected components, and full user flows, and how to manage test data.

In plain words
What is it for?
Use it to plan test coverage, automate regression checks, structure browser tests with the Page Object Model, and prepare consistent data for integration and end-to-end tests.
Why use it?
It helps make automated tests faster, more reliable, easier to reuse, and focused on the most important risks.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the qa-testing plugin — 4 skills, 1 command, 5 agents shipped together

Good fit Use it to plan test coverage, automate regression checks, structure browser tests with the Page Object Model, and prepare consistent data for integration and end-to-end tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monumentalsystems/atlas-agent-teams/test-automation
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 MonumentalSystems/Atlas-Agent-Teams --skill test-automation
Clone the repo
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install qa-testing, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

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 test-automation

README.md
[![agentmods](https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/test-automation/github.svg)](https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/test-automation)
Your own site
<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/test-automation"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/test-automation/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 test-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/test-automation"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/test-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,070 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00010 $0.01070
Opus 5 $0.00005 $0.00535
Sonnet 5 $0.00002 $0.00214
Haiku 4.5 $0.00001 $0.00107

Measured 8d ago against content hash ad26c3ec412a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

test-automation 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 8d 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.

teams/qa-testing/skills/test-automation/SKILL.md · 165 lines

How it starts

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

Test Automation

Test Automation Strategies

Pyramid Approach

  • Unit Tests (70%): Fast, isolated tests for individual functions and methods
  • Integration Tests (20%): Tests that verify components work together
  • End-to-End Tests (10%): Tests that simulate real user flows through the application

Risk-Based Testing

  • Prioritize automation based on business risk and frequency of use
  • Focus on critical paths and high-value features first
  • Automate regression tests to prevent regressions

Test Data Management

  • Fixtures: Pre-defined test data sets for consistent test runs
  • Factories: Dynamic test data generation for flexibility
  • Test Builders: Fluent APIs for creating complex test objects
  • Data Seeding: Database seeding for integration and E2E tests

Test Design Patterns

Page Object Model (POM)

  • Encapsulate page elements and interactions in page objects
  • Separate test logic from page interaction logic
  • Improve test maintainability and reusability
  • Example structure:
    class LoginPage {
      constructor(page) {
        this.page = page;
        this.usernameInput = page.locator('#username');
        this.passwordInput = page.locator('#password');
        this.loginButton = page.locator('#login');
      }
      
      async login(username, password) {
        await this.usernameInput.fill(username);
        await this.passwordInput.fill(password);
        await this.loginButton.click();
      }
    }
    

Screenplay Pattern

  • Actor-based testing with human-like interactions
  • Composable abilities and tasks
  • More readable and maintainable test scenarios
  • Example structure:
    actor.attemptsTo(
      Navigate.to('/login'),
      Enter.theValue('username').into('#username'),
      Enter.theValue('password').into('#password'),
      Click.on('#login')
    );
    

Data-Driven Testing

  • Separate test logic from test data
  • Run same test with multiple data sets
  • Use CSV, JSON, or database for test data
  • Example structure:
    const testData = [
      { username: 'user1', password: 'pass1', expected: 'success' },
      { username: 'user2', password: 'pass2', expected: 'success' },
      { username: 'invalid', password: 'wrong', expected: 'failure' }
    ];
    
    testData.forEach(({ username, password, expected }) => {
      test(`login with ${username}`, async ({ page }) => {
        await login(page, username, password);
        await expect(page.locator('.status')).toHaveText(expected);
      });
    });
    

Read the full file on GitHub · 165 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. 8d ago First seen · 165 lines · 10 tokens per session scan A ad26c3ec412a

Subscribe to this mod's changes

test-automation is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 1,070 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-09-03.

Related

Other skills, from other repositories

axiom-testing

Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.

CharlesWiltgen/Axiom · 38 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

test-automation

Execute Vitest and Playwright test suites with result collection and failure analysis.

a5c-ai/babysitter · 0 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

prd-auto-test-loop

A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.

yunshu0909/yunshu_skillshub · 79 tokens

test-automation-expert

Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…

curiositech/some_claude_skills · 133 tokens