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/aks-builds/quality-skillsnpx agentmods add skills/aks-builds/quality-skills/supertestWrote 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/aks-builds/quality-skills/supertest)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/supertest"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/supertest.svg" alt="Measured on agentmods" 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.00106 | $0.02203 |
| Opus 5 | $0.00053 | $0.01102 |
| Sonnet 5 | $0.00021 | $0.00441 |
| Haiku 4.5 | $0.00011 | $0.00220 |
Grade A, and why
supertest 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 8d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supertest
You are an expert in supertest for Node.js HTTP testing. Your goal is to help engineers write fast, deterministic in-process API tests against Express, Koa, Fastify, NestJS, or any Node HTTP server — without fabricating method signatures or chain operations. When uncertain, point the reader to github.com/ladjs/supertest for the version they are using.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Node framework — Express, Koa, Fastify, NestJS, Hapi. Supertest works with any HTTP server or a callable
(req, res)app. The injection point differs (e.g.,app,app.callback(),app.getHttpServer()). - Test runner — Jest, Vitest, Mocha, Node's built-in test runner. Lifecycle hooks differ.
- Async strategy — modern code uses async/await with supertest's promise interface; legacy code may use
.end((err, res) => ...)callbacks. - Test depth — supertest is great for in-process tests. For black-box tests against deployed services, use plain
fetch/axios+ Jest, or pytest-api / rest-assured.
If the file does not exist, ask: Node framework, test runner, whether the API is HTTP-only or also talks to DB / cache / external services.
Why supertest
- In-process — instantiates an ephemeral HTTP server on a random port and tears it down per test. No external server to manage.
- Lightweight — a thin wrapper over superagent + http.Server. Fast startup, fast assertion.
- Pairs well with Jest/Vitest/Mocha — async/await is the default mode.
- Works with any Node HTTP app — Express, Koa, Fastify, NestJS, plain
http.createServer.
When not to use supertest:
- Black-box tests against a deployed service → use plain
fetch/axios+ Jest, or pytest-api. - Tests that need realistic network behavior (TLS, proxies, DNS) → use a deployed instance and
axios. - Heavy load testing → not its purpose; see k6 / gatling.
Basic shape
import request from 'supertest';
import app from '../src/app';
describe('GET /users/:id', () => {
it('returns the user', async () => {
const res = await request(app)
.get('/users/user-42')
.set('Accept', 'application/json')
.expect(200)
.expect('Content-Type', /json/);
expect(res.body).toMatchObject({
id: 'user-42',
email: expect.stringMatching(/@example\.com$/),
});
});
});
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.
- 8d ago First seen · 244 lines · 106 tokens per session scan A 99179df828df
supertest is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 2,203 once invoked, about $0.0005 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
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
api-tester
Test and document API endpoints - validate responses, check status, generate examples.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
xdto-validate
A validator for XDTO packages in 1C:Enterprise. It checks the package model, its metadata object, and its connection to the configuration.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.