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.
npx agentmods add skills/mtnyilmaz/agents/testing-engineernpx skills add mtnyilmaz/agents --skill testing-engineergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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 | $0.00050 | $0.01971 |
| Opus 5 | $0.00025 | $0.00986 |
| Sonnet 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 2d 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.
- 2d 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 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,971 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.
Other skills, from other repositories
cloudflare-registrar
Cloudflare Registrar: domain availability, prices, registration via mcporter.
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
weekly-report
Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…