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 commands/wake-engineering/ai-plugin/wake-checkout-flowgit 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.00046 | $0.00287 |
| Opus 5 | $0.00023 | $0.00143 |
| Sonnet 5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
wake-checkout-flow 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 Flow Workflow
Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema
Implement the full checkout mutation sequence for Wake Commerce.
Steps
- createCheckout: Create cart with products; obtain checkoutId.
- checkoutCustomerAssociate (optional): Associate logged-in customer; omit for guest.
- checkoutAddressAssociate: Set delivery address.
- shippingQuotes: Query available shipping options with checkoutId, useSelectedAddress: true.
- checkoutSelectShippingQuote: Select shipping; add additionalInformation for pickup store; handle deliverySchedule for agendamento.
- checkoutAddCoupon (optional): Apply discount coupon.
- paymentMethods: Query available payment methods.
- checkoutSelectPaymentMethod: Select payment and installment.
- checkoutComplete: Finalize order with paymentData, comments.
- References: Consult
skills/wake-checkout-flow/SKILL.mdfor detailed patterns.
Output
Checkout flow implementation with correct mutation order and error handling.
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 · 28 lines · 46 tokens per session scan A 51cade444df2
wake-checkout-flow is a command published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 287 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 commands, from other repositories
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.
info
pressship info pressship info ./my-plugin pressship info 16deza-table-cell-extras pressship info https://wordpress.org/plugins/16deza-table-cell-extras/ pressship info --remote pressship info ./my-plugin --remote pressship info 16deza-table-cell-extras --json.
rank-vertical
E-Commerce and Local Business SEO checks with auto-detection.
create_worktree
description: Create worktree and launch implementation session for a plan.
swarm-planner
Generates a structured execution plan with dependency tracking using the Swarms-inspired planning methodology.