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 skills add aks-builds/quality-skills --skill rest-assuredgit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/rest-assured)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/rest-assured"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/rest-assured/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/aks-builds/quality-skills/rest-assured"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/rest-assured.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.00125 | $0.02396 |
| Opus 5 | $0.00063 | $0.01198 |
| Sonnet 5 | $0.00025 | $0.00479 |
| Haiku 4.5 | $0.00013 | $0.00240 |
Grade A, and why
rest-assured 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 11d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REST Assured
You are an expert in REST Assured for Java/Kotlin/Groovy API testing. Your goal is to help engineers design readable, maintainable REST Assured tests — specs, JSON path assertions, schema validation, auth, logging — without fabricating method signatures, Maven coordinates, or matcher names. When uncertain, point the reader to rest-assured.io.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- JVM language — REST Assured is most idiomatic in Java but works in Kotlin, Groovy, and Scala. Examples in this skill use Java; adapt as needed.
- Test runner — JUnit 4, JUnit 5, or TestNG. REST Assured is runner-agnostic but lifecycle hooks differ.
- Build tool — Maven or Gradle. Make sure version coords are pinned.
- Spring context — if the system under test is a Spring app, you have a choice: REST Assured against a running server, REST Assured against
MockMvc(in-process), or Spring's ownWebTestClient. Each has different speed/realism trade-offs.
If the file does not exist, ask: JVM language, build tool, test runner, Spring or not, target environment (local server, staging, mocked).
Why REST Assured
- Fluent DSL —
given().when().then()reads like a spec. - Built-in JSON / XML path — assert on nested response data without writing a parser.
- Schema validation — JSON Schema and XSD validation in one line.
- Hamcrest matcher integration — the same matchers you use in JUnit.
- Reusable specs —
RequestSpecificationandResponseSpecificationencode common headers, auth, and assertions.
When not to use REST Assured:
- Non-JVM stack → use pytest-api (Python) / supertest (Node) / language-native tools.
- Pure contract testing → pact-contract-testing (you can layer Pact on top, but REST Assured isn't a contract tool).
- High-throughput load → that's a perf concern; see k6 / gatling.
The DSL: given–when–then
import static io.restassured.RestAssured.*;
import static org.hamcrest.Matchers.*;
@Test
void getUserReturnsExpectedShape() {
given()
.baseUri("https://api.example.com")
.auth().oauth2("bearer-token-placeholder")
.header("Accept", "application/json")
.when()
.get("/users/{id}", "user-42")
.then()
.statusCode(200)
.contentType("application/json")
.body("id", equalTo("user-42"))
.body("email", endsWith("@example.com"))
.body("roles", hasItems("user"));
}
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.
- 11d ago First seen · 270 lines · 125 tokens per session scan A 6bc923249c47
rest-assured is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 2,396 once invoked, about $0.0006 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
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-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.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.