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.
npx skills add bishopZ/2026-Boilerplate --skill migrate-api-to-graphql-clientgit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWrote 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.
[](https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-api-to-graphql-client)<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.
<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>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.5 | $0.00011 | $0.00207 |
| Sonnet 5.5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 1mo 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.
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.mdwith GraphQL migration status and contract guidance. - Update
docs/ARCHITECTURE.mdwhen 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
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.
- 1mo ago First seen · 66 lines · 27 tokens per session scan A 0eb6e577fd02
migrate-api-to-graphql-client is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
prisma-8
Use when working in a project that depends on @prisma/orm-postgres, @prisma/orm-sqlite, or @prisma/orm-mongo (Prisma 8, formerly Prisma Next): editing contract.prisma or a contract.ts builder, running prisma contract emit, planning or applying migrations, editing migration.ts, writing db.orm / db.sql / db.query…
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…
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.
nodejs-expert
Expert-level Node.js backend development with Express, async patterns, streams, performance optimization, and production best practices. Use when the user mentions JavaScript, backend, Express, or async, or when the task involves Modern Node.js Features, Express Framework, File System Operations, or HTTP Requests.
netsuite-sdf-safe-guide
Comprehensive NetSuite SDF best practices based on the SAFE Guide (12 principles + appendices). Generates Object XML for all 14 script types, enforces governance limits, security patterns, and defensive coding. Includes N/cache, N/query, concurrency limits, OAuth 2.0 guidance, legacy TBA guardrails, CustomTool runtime…
netsuite-ai-connector-instructions
NetSuite Intelligence skill — teaches AI the correct tool selection order, output formatting, domain knowledge, multi-subsidiary and currency handling, and SuiteQL safety checklist for any AI + NetSuite AI Service Connector session.