← ClaudeAtlas

graphql-complexity-limit-testerlisted

Use when a GraphQL API must be hardened or audited against denial of service and schema disclosure. Sends over-limit depth and cost queries and asserts they are rejected, proving graphql-depth-limit, cost analysis or graphql-armor are enforced; covers introspection and persisted-query allowlists.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# graphql-complexity-limit-tester ## Overview The introspection attack-surface catalog ([references/introspection.md](references/introspection.md)) names query-depth limiting and query-cost limiting as key DoS mitigations, but nothing in that catalog executes a test. This skill closes that gap: it authors tests that send an over-limit query and assert a validation error is returned _before_ any resolver runs. The strongest request-layer mitigation - persisted-query allowlisting - is cataloged in [references/persisted-queries.md](references/persisted-queries.md). Three library families are covered: - `graphql-depth-limit` (npm: `graphql-depth-limit`, canonical repo `github.com/stems/graphql-depth-limit`, per npm registry [registry.npmjs.org/graphql-depth-limit](https://registry.npmjs.org/graphql-depth-limit/latest)) - `depthLimit(n)` validation rule, drop-in for Apollo or express-graphql. - `graphql-cost-analysis` (npm: `graphql-cost-analysis`, repo `github.com/pa-bru/graphql-cost-analysis`, per [github.com/pa-bru/graphql-cost-analysis](https://github.com/pa-bru/graphql-cost-analysis)) - `costAnalysis({ maximumCost })` validation rule; queries above the threshold are rejected. - `@escape.tech/graphql-armor` (repo `github.com/Escape-Technologies/graphql-armor`, docs [escape.tech/graphql-armor/docs](https://escape.tech/graphql-armor/docs/getting-started)) - `max-depth` plugin: default `n = 6` (per [escape.tech/graphql-armor/docs/plugins/max-depth](h