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.
git clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-builderWrote 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/commands/khadinakbarlabs/shopify-app-builder/migrate-rest-to-graphql)<a href="https://agentmods.dev/commands/khadinakbarlabs/shopify-app-builder/migrate-rest-to-graphql"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/migrate-rest-to-graphql/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/commands/khadinakbarlabs/shopify-app-builder/migrate-rest-to-graphql"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/migrate-rest-to-graphql.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.00022 | $0.00778 |
| Opus 5 | $0.00011 | $0.00389 |
| Sonnet 5 | $0.00004 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
migrate-rest-to-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 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate REST to GraphQL
You are converting Shopify REST API calls to GraphQL for improved performance, better cost efficiency, and future API compatibility.
Migration Assessment
-
Inventory REST endpoints
- Search codebase for /admin/api/[year]/[resource].json endpoints
- Document each REST call: method (GET/POST/PUT), resource type, usage frequency
- Identify which endpoints have GraphQL query equivalents
- Map REST response fields to GraphQL query fields (field names may differ)
- Reference skill: API versioning and migration (02_apis.md)
-
Assess cost-benefit
- Calculate REST endpoint cost (count-based billing, higher for batch operations)
- Estimate GraphQL query cost for equivalent operation (field-level granularity)
- Example: REST GET /products.json (100 fields) = 10 API calls/s; GraphQL query (10 fields) = 75 points
- Identify high-impact migrations (batch endpoints, pagination-heavy queries)
- Reference skill: GraphQL cost optimization (02_apis.md)
-
Plan migration priority
- Prioritize REST endpoints with highest call volume
- Start with read operations (GET) before mutations
- Group related endpoints for batch migration (product endpoints together)
- Plan rollback strategy for each migration phase
- Reference skill: migration planning (02_apis.md)
Implementation
-
Convert REST to GraphQL queries
- Rewrite the REST products request as a GraphQL query using the latest supported stable API version
- Add pagination with first: 25, after: "[cursor]" to REST limit parameters
- Map REST filters (status=active) to GraphQL query filters
- Include only needed fields (don't request full object if only id, title needed)
- Reference skill: GraphQL query construction (02_apis.md)
-
Implement GraphQL client
- Replace REST fetch calls with GraphQL client (@shopify/graphql-request or Apollo)
- Update authentication header: X-Shopify-Access-Token (same as REST)
- Convert response parsing: REST array becomes GraphQL data.resources.edges
- Implement error handling for GraphQL errors (different structure than REST)
- Reference skill: GraphQL client implementation (02_apis.md)
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 · 77 lines · 22 tokens per session scan A c15f379d43bd
migrate-rest-to-graphql is a command published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 778 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-31.
Other commands, from other repositories
tray-referencia-api
Referência rápida de todos os endpoints da API da Tray, aceita nome do recurso como filtro.
tray-setup
Guia rápido para configuração inicial de integração com a API da Tray.
tray-validar-integracao
Valida o código de integração com a Tray verificando problemas comuns e boas práticas.
init
Initialize configurations for Supabase local development.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.