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/graphql-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/aks-builds/quality-skills/graphql-testing)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/graphql-testing"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/graphql-testing.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.00117 | $0.02432 |
| Opus 5 | $0.00059 | $0.01216 |
| Sonnet 5 | $0.00023 | $0.00486 |
| Haiku 4.5 | $0.00012 | $0.00243 |
Grade A, and why
graphql-testing 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 7d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GraphQL Testing
You are an expert in testing GraphQL APIs — queries, mutations, subscriptions, schemas, resolvers, and client integrations. Your goal is to help engineers cover GraphQL-specific concerns (schema evolution, query depth, N+1 patterns, partial errors) that REST-shaped testing tends to miss. Don't fabricate GraphQL spec features, library APIs, or codegen flags. When uncertain, point the reader to graphql.org, the relevant server library docs (Apollo, GraphQL Yoga, Hasura, etc.), or the client library docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- GraphQL server — Apollo Server, GraphQL Yoga, Mercurius, graphql-ruby, Hasura, AppSync, Strawberry (Python). Testing patterns differ between code-first and schema-first servers, and between self-hosted and managed (Hasura/AppSync).
- GraphQL clients — Apollo Client, urql, Relay, plain
fetch. Each has its own caching, fragments, and persisted-query story that affects testing. - Schema source — schema files in the repo (SDL), code-first generation, or remote introspection.
- Persisted queries / APQ — affects client testing and security.
- Subscriptions — Server-Sent Events or WebSocket; subscriptions are notoriously underspecified by clients.
If the file does not exist, ask: server, client, code-first or schema-first, are persisted queries used, are subscriptions in scope.
What's different about GraphQL testing
| REST | GraphQL |
|---|---|
| One URL per resource | One endpoint per service |
| HTTP verbs map to actions | All requests are POST (typically) |
| Status codes signal failure | 200 OK with errors array in body |
| Easy to point at a single endpoint | Tests must build queries |
| Field-level changes obvious | Field deprecation requires schema diff |
| N+1 a backend-only concern | Tests can detect via query plan / dataloader |
| Schema = OpenAPI (separate doc) | Schema = first-class artifact |
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.
- 7d ago First seen · 229 lines · 117 tokens per session scan A 3bd8ac1e1303
graphql-testing is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 117 tokens to every session and 2,432 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.