What is migrate-api-to-graphql-client?

A migration guide for changing a client application from REST calls to GraphQL, a system where clients request specific data through named operations. It supports typed operations and allows both approaches to work during the transition.

Use it to add the GraphQL client setup, organize queries and related types, and create feature-level adapters or hooks. It is for gradually moving client data access from REST endpoints to GraphQL operations.

It reduces the risk of breaking authentication or existing features while replacing one API style with another. The migration can happen one feature area at a time, with REST kept as a fallback until GraphQL matches it.

migrate-api-to-graphql-client — Skill for Claude Code and Codex by bis

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.

Any agent

npx skills add bishopZ/2026-Boilerplate --skill migrate-api-to-graphql-client

Clone the repo

git clone --depth 1 https://github.com/bishopZ/2026-Boilerplate

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client/github.svg)](https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client)

Your own site

<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 518 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.00518
Opus 5	$0.00014	$0.00259
Sonnet 5	$0.00005	$0.00104
Haiku 4.5	$0.00003	$0.00052

Measured 10d ago against content hash 0eb6e577fd02, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

migrate-api-to-graphql-client 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 10d 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.

skills/migrate-api-to-graphql-client/SKILL.md · 66 lines

How it starts

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

Migrate API to GraphQL Client Path

Use this skill when a task asks to move from REST-first client calls to a GraphQL client model.

Goal

Introduce a GraphQL client path that can coexist with current REST endpoints during migration, then progressively replace REST usage.

Migration Principles

Do not break existing auth/session behavior during rollout.
Keep migration incremental: one feature domain at a time.
Treat GraphQL as the new data contract layer while REST stays as fallback until parity is complete.

Files To Update

1) GraphQL client foundation

Add a GraphQL client dependency (for example: Apollo Client, urql, or graphql-request) based on task constraints.
Add shared client initialization under src/client/data/ (for example: graphql-client.ts).
Configure credential handling for cookie-based auth where needed.

2) Schema and operation organization

Add a clear folder layout for operations/fragments/types (for example: src/client/data/graphql/).
Keep operation names domain-oriented and stable.
Prefer generated TypeScript types when codegen is available.

3) Feature rollout

Create feature-level adapters/hooks that hide transport details from components.
Migrate domain by domain (auth/session first if requested, then product/preferences, etc.).
Keep equivalent behavior with current REST flows while both paths coexist.

4) REST deprecation plan

Document which REST endpoints are superseded.
Keep compatibility endpoints active until all consuming code is migrated.
Remove legacy code only after tests prove GraphQL parity.

5) Docs and changelog

Update docs/API.md with GraphQL migration status and contract guidance.
Update docs/ARCHITECTURE.md when transport/data layers change.
Add migration notes under CHANGELOG.md → Unreleased.

Validation Checklist

Run npm run lint
Run npm run type-check
Run focused E2E tests for migrated feature paths
Verify auth/session cookies still work correctly with GraphQL requests
Verify GraphQL errors are surfaced via existing error handling patterns

Read the full file on GitHub · 66 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.

10d ago First seen · 66 lines · 27 tokens per session scan A 0eb6e577fd02

Subscribe to this mod's changes

migrate-api-to-graphql-client is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 518 once invoked, about $0.0001 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-30.

Backend and APIs Frontend javascript nodejs passportjs vite

typescript-expert

Expert-level TypeScript development with modern tooling, advanced types, and best practices. Use this skill for TypeScript projects requiring type-safe code, modern bundling, and comprehensive testing.

personamanagmentlayer/pcl · 40 tokens

prisma-8

Comprehensive guide for building with Prisma 8 (Prisma Next), the contract-first data layer. Use whenever working on Prisma code in a project that uses it — authoring or editing the data contract (contract.prisma, PSL, TypeScript builders), migrations, queries (db.orm / db.sql), runtime wiring (db.ts, middleware…

prisma/orm · 220 tokens

hunt-nodejs

Hunt Node.js specific vulnerabilities — Prototype Pollution → RCE chains (lodash/merge/assign), Express trust proxy misconfiguration, childprocess/eval injection, template engine SSTI (EJS/Pug/Handlebars), path traversal in file servers, require() injection, environment variable exfil via /proc/self/environ. Use when…

uphiago/recon-skills · 87 tokens

menu-recipes

Recipes composed on the react-horizontal-scrolling-menu public API — NOT props: autoplay (setInterval + scrollNext gated on menuVisible), infinite loop/carousel (clone head/tail + scrollLeft teleport at seams), center on click (scrollToItem 'center'), save/restore scroll position (onUpdate, onInit, scrollContainer)…

asmyshlyaev177/react-horizontal-scrolling-menu · 145 tokens

menu-interactions

Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) => void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove, onMouseLeave, onTouchStart, onTouchMove, onTouchEnd) are handler factories (api) => (event) => void. Covers mouse…

asmyshlyaev177/react-horizontal-scrolling-menu · 147 tokens

consuming-endpoints-from-client-code

Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL codename vs insight breakdown property), handling rate-limit and materialised-endpoint error…

PostHog/posthog · 105 tokens