agents: Skill for Claude Code

.agents/skills/testing-engineer/SKILL.md

testing-engineer is a skill for Claude Code, Codex from mtnyilmaz/agents. It costs 50 tokens per session (1,971 once invoked), scanned A, original, MIT.

A testing specialist for Vitest, Playwright, pytest, Go testing, and PHPUnit/Pest. Tests are checks that code behaves correctly; end-to-end tests can exercise complete user journeys in a browser.

In plain words
What is it for?
Use it to write or debug tests, set up testing infrastructure, mock dependencies, and cover flows such as login, checkout, and signup.
Why use it?
It helps choose suitable unit, integration, and browser-level tests, while also addressing test setup, mocks, and flaky tests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is mtnyilmaz/agents's own configuration. It tells Claude Code and Codex how to work on agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mtnyilmaz/agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mtnyilmaz/agents/main/.agents/skills/testing-engineer/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mtnyilmaz/agents

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mtnyilmaz/agents/testing-engineer"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/testing-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,971 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.00050 $0.01971
Opus 5.5 $0.00020 $0.00788
Sonnet 5.5 $0.00010 $0.00394
Haiku 4.5 $0.00005 $0.00197

Measured 1mo ago against content hash ddb20c7ade3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-engineer 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 1mo 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.

.agents/skills/testing-engineer/SKILL.md · 323 lines

How it starts

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

Testing Engineer

Expert in writing production-quality tests. Focused on Vitest, Playwright, pytest, and Go testing.

Test Strategy

E2E (Playwright)         → Critical user flows (login, checkout, signup)
Integration (Vitest)     → API endpoints, service layer, DB queries
Unit (Vitest)            → Business logic, utilities, validation, transformations

TypeScript / Vitest

Setup

// vitest.config.ts
import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    environment: 'node',        // for API tests
    // environment: 'jsdom',    // for React component tests
    setupFiles: ['./src/test/setup.ts'],
    coverage: {
      provider: 'v8',
      reporter: ['text', 'html'],
      exclude: ['**/node_modules/**', '**/test/**'],
    },
  },
})

Unit Test Template

import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest'
import { UserService } from './user.service'
import { prismaMock } from '@/test/mocks/prisma'

describe('UserService', () => {
  let service: UserService

  beforeEach(() => {
    service = new UserService(prismaMock)
  })

  afterEach(() => {
    vi.clearAllMocks()
  })

  describe('createUser', () => {
    it('should hash password before saving', async () => {
      // Arrange
      const input = { email: '[email protected]', password: 'plain123' }
      prismaMock.user.create.mockResolvedValue({
        id: '1',
        email: input.email,
        password: 'hashed',
        createdAt: new Date(),
      })

      // Act
      const result = await service.createUser(input)

      // Assert
      expect(prismaMock.user.create).toHaveBeenCalledWith({
        data: expect.objectContaining({
          email: input.email,
          password: expect.not.stringContaining('plain123'),
        }),
      })
    })

    it('should throw ConflictError when email exists', async () => {
      prismaMock.user.create.mockRejectedValue(
        new Prisma.PrismaClientKnownRequestError('', { code: 'P2002', clientVersion: '' })
      )

      await expect(service.createUser(input)).rejects.toThrow(ConflictError)
    })
  })
})

Read the full file on GitHub · 323 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 323 lines · 50 tokens per session scan A ddb20c7ade3f

Subscribe to this mod's changes

testing-engineer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 1,971 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-08-31.

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

06-test

Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…

ai-driven-dev/framework · 69 tokens