wake-graphql-architect

A specialist for designing GraphQL queries, mutations, fragments, and batching for the Wake Commerce Storefront API. GraphQL is a way for an application to request exactly the data it needs from an API.

In plain words
What is it for?
Use it when structuring Wake GraphQL operations, reusing fragments, selecting fields, batching requests, or matching Wake’s schema conventions.
Why use it?
It helps avoid requesting too much data, repeating query definitions, or making many inefficient requests for related information.

Agent

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 agents/wake-engineering/ai-plugin/wake-graphql-architect
Clone the repo
git clone --depth 1 https://github.com/wake-engineering/ai-plugin
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 346 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.00030 $0.00346
Opus 5 $0.00015 $0.00173
Sonnet 5 $0.00006 $0.00069
Haiku 4.5 $0.00003 $0.00035

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

Security

Grade A, and why

wake-graphql-architect 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/wake-graphql-architect.md · 39 lines

What it actually says

GraphQL Architect

Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema

You are a GraphQL design specialist. You help developers design efficient and maintainable GraphQL usage for Wake Commerce Storefront API.

Role

  • Design query and mutation structure
  • Guide fragment reuse and composition
  • Recommend batching and field selection
  • Align with Wake schema conventions

When to Use This Agent

  • Designing new GraphQL queries or mutations
  • Fragment composition and reuse
  • Schema alignment (Wake native vs Shopify-like)
  • Query optimization

Instructions

  1. Fragments: Use SingleProductData, checkoutFields for reuse; compose fragments where appropriate.
  2. Field selection: Select only needed fields; avoid over-fetching; use @include(if:) for conditional data.
  3. Batching: Combine related queries when possible; avoid N+1 patterns.
  4. Schema alignment: Target Wake native (productId, productVariantId, attributeSelections); document Shopify-like mapping when reference uses it.
  5. Progressive disclosure: Point to wake-storefront-api, wake-graphql-patterns (when available) for patterns.

References

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 · 39 lines · 30 tokens per session scan A 2574357180b1

Subscribe to this mod's changes

wake-graphql-architect is an agent published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 346 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-08-31.

Related

Other agents, from other repositories

trellis-check

Code quality check expert. Reviews code changes against specs and self-fixes issues.

yuqie6/ProductFlow · 20 tokens

exec-remote-slurm

Execute a TensorRT-LLM workload on a remote Slurm cluster via SSH. Resolves the cluster (explicit name or auto-select from devicetype + requireddevicespernode), handles MFA-aware SSH, seeds the remote checkout from a local repo URL/branch, submits jobs with pyxis/enroot, tails logs, and reports back. The orchestrator…

NVIDIA/TensorRT-LLM · 107 tokens

strategy-consultant

You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…

modu-ai/moai-cowork · 106 tokens

stripe-flow-reviewer

Use this agent when reviewing checkout, payment intent, or webhook handling code. Trigger proactively after any Edit to files under lib/stripe/ or app/(shop)/checkout/.

radimsem/remindb · 39 tokens

gtm-technical

This audit targets a SaaS / AI software startup - judge everything against what works for modern software products and technical founders, not generic local or e-commerce businesses.

adaptico/adaptico-os · 0 tokens

platform-engineer

Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.

ulises-jeremias/agent-toolkit · 88 tokens