agentleFS
Sign inStart free
JustineDevsJustineDevs/premortem/.agents/skills/graphql-and-hidden-parameters/SKILL.md

graphql-and-hidden-parameters

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

GraphQL and hidden parameter testing playbook. Use when exploring introspection, batching, undocumented fields, hidden parameters, schema abuse, and GraphQL authorization gaps.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If introspection is restricted, continue with:

    line 22
  2. Distinctive:

    If hidden fields affect privilege: api authorization and bola

    line 48
  3. Distinctive:

    If GraphQL batching changes auth or rate behavior: api auth and jwt abuse

    line 49
  4. Distinctive:

    If endpoint discovery is incomplete: api recon and docs

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SKILL: GraphQL and Hidden Parameters — Introspection, Batching, and Undocumented Fields

AI LOAD INSTRUCTION: Use this skill when GraphQL exists or when REST documentation suggests optional, deprecated, or undocumented fields. Focus on schema discovery, hidden parameter abuse, and batching as a force multiplier.

1. GRAPHQL FIRST PASS

query { __typename }
query {
  __schema {
    types { name }
  }
}

If introspection is restricted, continue with:

  • field suggestions and error-based discovery
  • known type probes like __type(name: "User")
  • JS and mobile bundle route extraction

2. HIGH-VALUE GRAPHQL TESTS

ThemeExample
IDORuser(id: "victim")
batchingarray of login or object fetch operations
hidden fieldsadmin-only fields exposed in type definitions
nested authz gapsrelated object fields with weaker checks

3. HIDDEN PARAMETER DISCOVERY

Look for:

  • fields present in admin docs but not public docs
  • additionalProperties or permissive schemas
  • frontend code using richer request bodies than visible UI controls
  • mobile endpoints carrying role, org, feature-flag, or internal filter fields

4. NEXT ROUTING

  • If hidden fields affect privilege: api authorization and bola
  • If GraphQL batching changes auth or rate behavior: api auth and jwt abuse
  • If endpoint discovery is incomplete: api recon and docs

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free