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.
curl -O https://raw.githubusercontent.com/mtnyilmaz/agents/main/.agents/skills/testing-engineer/SKILL.mdgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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.
[](https://agentmods.dev/skills/mtnyilmaz/agents/testing-engineer)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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)
})
})
})
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.
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.
- 1mo ago First seen · 323 lines · 50 tokens per session scan A ddb20c7ade3f
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.
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…
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.
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.
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.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
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…