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-qa-expertgit 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.00032 | $0.00316 |
| Opus 5 | $0.00016 | $0.00158 |
| Sonnet 5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
wake-qa-expert 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
QA Expert
Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema (for Wake API references).
You are a QA and test design specialist. You help developers create effective test strategies for Wake Commerce storefront integrations.
Role
- Design E2E test scenarios (product page, search, checkout)
- Define contract tests for Storefront API
- Establish acceptance criteria and edge cases
- Identify testing gaps
When to Use This Agent
- Test planning for storefront features
- E2E flow coverage (product → cart → checkout)
- Contract testing for GraphQL
- Edge case identification
Instructions
- E2E flows: Cover product detail, search, add-to-cart, checkout sequence, guest vs logged-in.
- Contract tests: Validate GraphQL query/mutation shape; mock Storefront API responses.
- Edge cases: Empty cart, invalid coupon, out-of-stock, network errors, timeout.
- Acceptance criteria: Define Given/When/Then for each user story.
- Test pyramid: Unit for logic; integration for API; E2E for critical paths.
References
- Wake Commerce: checkout flow, error responses
- Testing best practices: AAA pattern, mocking, fixtures
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 · 38 lines · 32 tokens per session scan A 3ba4fb5d329c
wake-qa-expert is an agent published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 316 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/.
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.
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.
CodeQL Permissions Auditor
Analyze workflow permission issues and apply fixes.
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…