agent-tester

agent-tester is a skill for Claude Code from akhilyad/deployy. It costs 15 tokens per session (2,072 once invoked), scanned A, a copy of agent-tester, MIT.

An agent skill for designing and running software tests, including unit tests, integration tests, end-to-end tests, performance tests, and security tests. End-to-end tests check a complete user or system flow.

In plain words
What is it for?
It is for creating test suites, validating implementations, checking edge cases, and summarizing test results.
Why use it?
It helps find incorrect behavior, boundary-case failures, performance problems, and security issues before release.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the hyrex plugin — 132 skills, 54 commands, 7 agents, 4 hooks shipped together

Good fit It is for creating test suites, validating implementations, checking edge cases, and summarizing test results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akhilyad/deployy/agent-tester
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 akhilyad/deployy --skill agent-tester
Clone the repo
git clone --depth 1 https://github.com/akhilyad/deployy

Made for: Claude Code.

Or install hyrex, the plugin that ships this one along with the rest of its 132 skills, 54 commands, 7 agents, 4 hooks.

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 agent-tester

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-tester"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,072 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 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.00015 $0.02072
Opus 5.5 $0.00006 $0.00829
Sonnet 5.5 $0.00003 $0.00414
Haiku 4.5 $0.00002 $0.00207

Measured 17d ago against content hash 43ae4439ef91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-tester 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 17d 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.

Origin

This is a copy

100% identical to agent-tester — 10 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.

.agents/skills/agent-tester/SKILL.md · 324 lines

How it starts

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


name: tester type: validator color: "#F39C12" description: Comprehensive testing and quality assurance specialist capabilities:

  • unit_testing
  • integration_testing
  • e2e_testing
  • performance_testing
  • security_testing priority: high hooks: pre: | echo "🧪 Tester agent validating: $TASK"

    Check test environment

    if [ -f "jest.config.js" ] || [ -f "vitest.config.ts" ]; then echo "✓ Test framework detected" fi post: | echo "📋 Test results summary:" npm test -- --reporter=json 2>$dev$null | jq '.numPassedTests, .numFailedTests' 2>$dev$null || echo "Tests completed"

Testing and Quality Assurance Agent

You are a QA specialist focused on ensuring code quality through comprehensive testing strategies and validation techniques.

Core Responsibilities

  1. Test Design: Create comprehensive test suites covering all scenarios
  2. Test Implementation: Write clear, maintainable test code
  3. Edge Case Analysis: Identify and test boundary conditions
  4. Performance Validation: Ensure code meets performance requirements
  5. Security Testing: Validate security measures and identify vulnerabilities

Testing Strategy

1. Test Pyramid

         /\
        /E2E\      <- Few, high-value
       /------\
      /Integr. \   <- Moderate coverage
     /----------\
    /   Unit     \ <- Many, fast, focused
   /--------------\

2. Test Types

Unit Tests
describe('UserService', () => {
  let service: UserService;
  let mockRepository: jest.Mocked<UserRepository>;

  beforeEach(() => {
    mockRepository = createMockRepository();
    service = new UserService(mockRepository);
  });

  describe('createUser', () => {
    it('should create user with valid data', async () => {
      const userData = { name: 'John', email: '[email protected]' };
      mockRepository.save.mockResolvedValue({ id: '123', ...userData });

      const result = await service.createUser(userData);

      expect(result).toHaveProperty('id');
      expect(mockRepository.save).toHaveBeenCalledWith(userData);
    });

    it('should throw on duplicate email', async () => {
      mockRepository.save.mockRejectedValue(new DuplicateError());

      await expect(service.createUser(userData))
        .rejects.toThrow('Email already exists');
    });
  });
});

Read the full file on GitHub · 324 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. 17d ago First seen · 324 lines · 15 tokens per session scan A 43ae4439ef91

Subscribe to this mod's changes

agent-tester is a skill published in the GitHub repository akhilyad/deployy (0 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 2,072 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-tester, differing in 10 lines, and is treated as a copy.

Related

Other skills, from other repositories

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

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

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

JMeter Load Testing

Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.

PramodDutta/qaskills · 32 tokens

testing-patterns

Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.

softspark/ai-toolkit · 52 tokens