Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/echoVic/boss-skillnpx agentmods add skills/echovic/boss-skill/api-testingWrote 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/echovic/boss-skill/api-testing)<a href="https://agentmods.dev/skills/echovic/boss-skill/api-testing"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/api-testing/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/echovic/boss-skill/api-testing"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/api-testing.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.00041 | $0.03097 |
| Opus 5.5 | $0.00016 | $0.01239 |
| Sonnet 5.5 | $0.00008 | $0.00619 |
| Haiku 4.5 | $0.00004 | $0.00310 |
Grade A, and why
qa/api-testing scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
res = requests.post(f"{BASE_URL}/api/users", json={"name": "Alice", "email": "[email protected]"}) How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API 接口测试方法论
参考开源实践:Supertest、REST Assured、Postman/Newman、HTTPie、Testcontainers
适用场景
- 后端 API 端点需要功能验证
- 需要测试接口边界值、错误处理、权限控制
- 需要验证 API 契约(请求/响应 schema 一致性)
- 需要覆盖认证、授权、越权等安全场景
- 需要测试完整业务流程的 API 链路
测试类型矩阵
| 测试类型 | 目的 | 工具 | 示例 |
|---|---|---|---|
| 功能测试 | 验证接口正常行为 | Supertest / REST Assured | 创建资源返回 201 |
| 边界测试 | 验证边界值和错误处理 | Supertest | 空 payload、超长字符串、非法 ID |
| 安全测试 | 认证、授权、越权 | Supertest + auth header | 无 Token 访问受保护资源 |
| 契约测试 | 请求/响应 schema 一致性 | Zod / JSON Schema | 响应字段类型校验 |
| 流程测试 | 多接口业务链路 | Supertest 链式调用 | 注册→登录→下单→支付 |
1. RESTful API 测试
1.1 Node.js (Supertest + Jest/Vitest)
// tests/api/users.test.ts
import request from 'supertest';
import { app } from '../../src/app';
describe('User API', () => {
describe('POST /api/users', () => {
it('creates user with valid data', async () => {
const res = await request(app)
.post('/api/users')
.send({ name: 'Alice', email: '[email protected]' })
.expect(201)
.expect('Content-Type', /json/);
expect(res.body.success).toBe(true);
expect(res.body.data).toMatchObject({ name: 'Alice', email: '[email protected]' });
expect(res.body.data.id).toBeDefined();
});
it('rejects empty name with 400', async () => {
const res = await request(app)
.post('/api/users')
.send({ name: '', email: '[email protected]' })
.expect(400);
expect(res.body.error.code).toBe('VALIDATION_ERROR');
});
it('rejects duplicate email with 409', async () => {
await request(app).post('/api/users').send({ name: 'A', email: '[email protected]' });
const res = await request(app)
.post('/api/users')
.send({ name: 'B', email: '[email protected]' })
.expect(409);
expect(res.body.error.code).toBe('CONFLICT');
});
});
});
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.
- today First seen · 400 lines · 41 tokens per session scan A 69c3363b1c81
qa/api-testing is a skill published in the GitHub repository echoVic/boss-skill (544 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 3,097 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-28.
Other skills, from other repositories
convex-test
Generate convex-test tests for the app's Convex functions.
validate-contracts
Assert data shape consistency across system boundaries — live API responses against JSON Schema, key-set comparison across layers, data shape validation for migrations and exports. Catches silent data corruption before deploy.
Contract Test Generator
Generate consumer-driven contract tests using Pact framework to verify API provider-consumer compatibility and prevent integration breaking changes.
api-testing-rest
Comprehensive RESTful API testing patterns covering HTTP methods, status codes, request/response validation, authentication, error handling, and contract testing.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
playwright-api
API testing skill using Playwright's built-in APIRequestContext for RESTful service validation, authentication flows, and API contract verification.