graphql

Guidance for building GraphQL APIs, interfaces where clients request exactly the data they need through a typed schema.

In plain words
What is it for?
Designing schemas, queries, mutations, subscriptions, resolvers, input types, filters, and client integrations with Apollo or urql.
Why use it?
It helps organise flexible queries and related data while addressing validation, authentication, pagination, errors, and repeated database queries.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/plazmodium/odin-workflow/graphql
Any agent
npx skills add Plazmodium/odin-workflow --skill graphql
Clone the repo
git clone --depth 1 https://github.com/Plazmodium/odin-workflow

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,710 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.02710
Opus 5 $0.00016 $0.01355
Sonnet 5 $0.00006 $0.00542
Haiku 4.5 $0.00003 $0.00271

Measured 2d ago against content hash 54366a7142f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

graphql 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 2d 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.

agents/skills/api/graphql/SKILL.md · 549 lines

How it starts

The opening of the file, as written. The whole thing — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GraphQL API Design

Instructions

  1. Assess the API need: Flexible queries, real-time data, or complex relationships.
  2. Follow GraphQL conventions:
    • Schema-first or code-first approach
    • Proper type definitions
    • N+1 query prevention with DataLoader
    • Input validation
  3. Provide complete examples: Include schema, resolvers, and client queries.
  4. Guide on best practices: Pagination, error handling, authentication.

Schema Design

Basic Types

type User {
  id: ID!
  email: String!
  name: String!
  avatar: String
  role: Role!
  posts: [Post!]!
  createdAt: DateTime!
  updatedAt: DateTime!
}

type Post {
  id: ID!
  title: String!
  content: String!
  published: Boolean!
  author: User!
  comments: [Comment!]!
  tags: [Tag!]!
  createdAt: DateTime!
}

enum Role {
  USER
  ADMIN
  MODERATOR
}

scalar DateTime

Input Types

input CreateUserInput {
  email: String!
  name: String!
  password: String!
  role: Role = USER
}

input UpdateUserInput {
  email: String
  name: String
  avatar: String
}

input PostFilters {
  published: Boolean
  authorId: ID
  tags: [String!]
  search: String
}

Queries and Mutations

type Query {
  # Single resource
  user(id: ID!): User
  post(id: ID!): Post

  # Collections with pagination
  users(
    first: Int
    after: String
    filter: UserFilter
  ): UserConnection!

  posts(
    first: Int
    after: String
    filter: PostFilters
    orderBy: PostOrderBy
  ): PostConnection!

  # Current user
  me: User
}

type Mutation {
  # User mutations
  createUser(input: CreateUserInput!): CreateUserPayload!
  updateUser(id: ID!, input: UpdateUserInput!): UpdateUserPayload!
  deleteUser(id: ID!): DeleteUserPayload!

  # Auth mutations
  login(email: String!, password: String!): AuthPayload!
  logout: Boolean!

  # Post mutations
  createPost(input: CreatePostInput!): Post!
  updatePost(id: ID!, input: UpdatePostInput!): Post!
  publishPost(id: ID!): Post!
  deletePost(id: ID!): Boolean!
}

type Subscription {
  postCreated: Post!
  commentAdded(postId: ID!): Comment!
}

Read the full file on GitHub · 549 lines

Changes

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.

  1. 2d ago First seen · 549 lines · 32 tokens per session scan A 54366a7142f1

Subscribe to this mod's changes

graphql is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 2,710 once invoked, about $0.0002 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-09-01.

Related

Other skills, from other repositories

pr

Use for any GitHub Pull Request work. Auto-detects lifecycle phase (create / update / report) from current state — only requires explicit command for status, comments, or merge. Triggered by /pr, 'PR', 'create PR', 'open PR', 'update PR', 'PR status', 'merge PR'. Suggests, never auto-creates without user invocation.

fo0/clawstash · 80 tokens

orca

Orchestrator mode — the default working mode of this project, not a toggle to find. The main agent does no task work itself: every unit goes to a role-framed subagent that inherits its model and effort, at most 5 in parallel unless overridden. Load it for the contract (roles, width, write scopes, verification), when…

fo0/clawstash · 120 tokens

scheduler

Use when work should happen later or repeatedly — 'schedule', 'routine', 'nightly', 'every morning', 'cron', 'remind me later', 'check back in an hour', 'watch this PR', '/scheduler'. Picks the right scheduler for the lifetime the work needs (cloud routine / session loop / desktop task), creates, lists, updates and…

fo0/clawstash · 95 tokens

ci

Use when the user wants CI status, failed-job logs, or help fixing a red build. Triggered by /ci, 'CI status', 'check the build', 'fix CI', 'why is CI failing', 'look at the build'. Auto-routes by state: status / logs / fix-proposal. Reads logs locally — never re-triggers builds without explicit user command.

fo0/clawstash · 80 tokens

done

Use when the user signals work completion with 'done', 'fertig', 'finished', 'abschluss', '/done'. Detects current branch (main vs feature), runs closure checks defined in CLAUDE.md, handles commit and push based on branch context, closes related GitHub issues, and reports a strict short summary.

fo0/clawstash · 67 tokens

gitnexus-cli

Use for read-only GitNexus index maintenance: check index status, list indexed repos, register or (re)build the index. Examples: "Is the GitNexus index current?", "List indexed repos", "Register this repo".

fo0/clawstash · 53 tokens