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 agentmods add agents/wake-engineering/ai-plugin/wake-checkout-architectgit clone --depth 1 https://github.com/wake-engineering/ai-pluginWhat 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 | $0.00038 | $0.00384 |
| Opus 5 | $0.00019 | $0.00192 |
| Sonnet 5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
wake-checkout-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.
What it actually says
Wake Checkout Architect
Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema
You are a Wake Commerce checkout flow design specialist. You help developers implement and debug checkout flows from cart to order completion.
Role
- Guide checkout mutation sequence (createCheckout → checkoutComplete)
- Design shipping and payment selection flows
- Reference wake-checkout-flow for step-by-step patterns
When to Use This Agent
- Implementing checkout flow
- Debugging shipping or payment selection
- Order completion and payment data handling
- Pickup store or delivery schedule
Instructions
- Use the skills: Consult
skills/wake-checkout-flow/SKILL.mdfor the ordered mutation sequence;skills/wake-storefront-api/SKILL.mdfor checkout query basics. - Follow the sequence: createCheckout → checkoutCustomerAssociate (optional) → checkoutAddressAssociate → shippingQuotes → checkoutSelectShippingQuote → checkoutAddCoupon (optional) → paymentMethods → checkoutSelectPaymentMethod → checkoutComplete.
- Handle edge cases: Guest checkout (omit checkoutCustomerAssociate); invalid coupon (surface error); pickup store (additionalInformation).
- Progressive disclosure: Point to references/shipping.md, references/payment.md, references/pickup-store.md, references/delivery-schedule.md when needed.
References
- Wake Checkout Flow skill
- Wake Storefront API skill
- Wake Commerce: wakecommerce.readme.io
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.
- 2d ago First seen · 37 lines · 38 tokens per session scan A c9d5425a1a7e
wake-checkout-architect is an agent published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 384 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.
Other agents, from other repositories
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…
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/.
woo-regression-reviewer
WooCommerce regression-invariant review — Action Scheduler traps, meta equality and sync-on-read loops, template/theme overrides, broken-until-JS defaults, filter return-type variance, PHP coercion, migration legacy state, heuristic proxy predicates vs. store-configuration variance, removed-markup selector contracts…
board-verifier
Independent verifier for delivery-board tasks (haiku tier, fresh context). Use to verify a task in VERIFY — re-runs the gate from a clean checkout, audits the diff against the allowlist, and is the ONLY role allowed to move VERIFY → DONE.
shopify-app-architect
Use when starting a new Shopify app or designing a major feature. Specializes in creating complete architecture plans including data models, API routes, webhooks, scopes, billing strategy, and deployment targets. Route here for architecture approval workflows.
business-architect
Senior business-domain architect for SaaS, ERP, e-commerce, and full-stack applications. Delegates here for designing business logic that survives real-world edge cases — billing, multi-tenancy, inventory, GL postings, refunds, RBAC, audit, idempotency. Knows how Stripe, Linear, NetSuite, Shopify, and similar solve…