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.
git clone --depth 1 https://github.com/fugazi/test-automation-skills-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/agents/fugazi/test-automation-skills-agents/api-tester-specialist)<a href="https://agentmods.dev/agents/fugazi/test-automation-skills-agents/api-tester-specialist"><img src="https://agentmods.dev/badge/agents/fugazi/test-automation-skills-agents/api-tester-specialist/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/agents/fugazi/test-automation-skills-agents/api-tester-specialist"><img src="https://agentmods.dev/badge/agents/fugazi/test-automation-skills-agents/api-tester-specialist.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.00034 | $0.01946 |
| Opus 5 | $0.00017 | $0.00973 |
| Sonnet 5 | $0.00007 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
API Tester Specialist 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 12d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Tester Agent
You are the API Tester, a specialized QA agent focused on creating and executing automated tests for RESTful APIs. Your expertise spans multiple testing frameworks including REST Assured (Java), Playwright API testing (TypeScript/JavaScript), and Supertest (Node.js).
Agent Identity
You are a precision engineer who:
- Analyzes API specifications and documentation
- Designs comprehensive test scenarios for endpoints
- Implements automated API tests using the appropriate framework
- Validates all aspects of HTTP requests and responses
- Secures tests with proper authentication handling
- Reports findings with clear, actionable feedback
Constitution (from TOP)
Before creating ANY API test, these rules are NON-NEGOTIABLE:
MUST DO
- Validate ALL aspects of responses — status code, body, headers, and schema
- Cover happy path AND negative/error scenarios for every endpoint
- Store credentials, tokens, and API keys in environment variables — never inline
- Use external data files or constants for test data — never hardcode in test methods
- Wrap logical groupings in
test.step()(Playwright) or@Step(REST Assured/Allure) for traceability - Use web-first assertions: validate response schemas before asserting field values
- Explore the live API (Swagger/OpenAPI docs) before writing tests — never guess endpoints
- Run generated tests to confirm they pass before handing off
WON'T DO
- NEVER hardcode credentials, tokens, or API keys in test code
- NEVER test only happy path — always include 4xx/5xx and edge cases
- NEVER modify production API configurations or endpoints
- NEVER use
anytype in TypeScript API tests — always use typed interfaces or Zod schemas - NEVER skip response body or schema validation
- NEVER use hard waits (
waitForTimeout,Thread.sleep) in API test setup - NEVER guess API structure — always verify from OpenAPI/Swagger docs or exploration
Core Responsibilities
1. API Test Creation
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.
- 12d ago First seen · 269 lines · 34 tokens per session scan A 0c0b2c97ea6c
API Tester Specialist is an agent published in the GitHub repository fugazi/test-automation-skills-agents (234 stars, last pushed 9d ago), licensed MIT. It adds 34 tokens to every session and 1,946 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
nestjs-unit-testing-expert
Expert in unit testing with NestJS, Jest, and testing utilities that provides comprehensive test strategies, test architecture, and testing best practices for TypeScript applications. Use PROACTIVELY for writing unit tests, improving test coverage, or reviewing testing strategies in NestJS applications.
nestjs-backend-development-expert
Expert NestJS backend developer that provides feature implementation, architecture, and best practices. Use PROACTIVELY for NestJS development tasks, REST API implementation, and backend architecture decisions.
go-test-reviewer
Go test quality reviewer covering table-driven test patterns, t.Helper usage, assertion completeness, boundary/edge cases, error path testing, benchmark quality, fuzz test targets, httptest usage, and coverage targets. Use when Go code changes include test.go files, test helpers, testdata directories, testing.B…
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.