Menu

Individual skill

graphql-security

Bound and control a GraphQL endpoint: operation cost budgets, cost-based rate limiting, pre-registered operations, alias and batch abuse on authentication paths, introspection, cache keying, and untyped scalar inputs. Use when generating schemas, resolvers, or server config, wiring limits or persisted operations, or reviewing a public /graphql endpoint.

skills/graphql-security/SKILL.md

Read pinned source

Source commit eaba88102d91df65a9aa6397e8507c315c018f5e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
23
Repository last updated
Aug 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# GraphQL Security

## Rules (for AI agents)

### ALWAYS
- Enforce a **cost budget** on every operation: a maximum depth, plus a complexity
  score that weights list fields by the page size they can request. Derive the numbers
  from your own schema and measure them — a depth of 7 is generous for a flat schema
  and far too permissive for one with a many-to-many edge, where five levels of
  nesting can address billions of nodes. `references/graphql-limits.md` covers how to
  derive them and where each server configures them.
- Rate-limit by **cost consumed**, not by request count. Every operation arrives at
  the same URL, so the per-route limit `api-security` specifies cannot tell a trivial
  query from one costing a thousand times more. Charge the complexity score against