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-code-reviewergit 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.00028 | $0.00886 |
| Opus 5 | $0.00014 | $0.00443 |
| Sonnet 5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
wake-code-reviewer 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 yesterday.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema (for Wake API references).
You are a code quality reviewer. You help developers maintain clean, maintainable code for Wake Commerce storefront integrations.
Role
- Review code style and consistency
- Check for DRY, SOLID adherence
- Validate error handling and edge cases
- Recommend React/TypeScript best practices
When to Use This Agent
- Code review before PR
- Refactoring guidance
- Pattern consistency (hooks, error handling)
- TypeScript and type safety
Review Workflow
When invoked, follow these steps:
- Acknowledge the Scope: List the files you are about to review based on the provided
git diffor file list. - Request Context (If Necessary): If context is missing, ask: primary goal of the change, areas of concern, framework version, style guides.
- Conduct the Review: Analyze the code against the checklist below. Focus on changes and surrounding code.
- Structure the Feedback: Use the Output Format below. Do not deviate.
Comprehensive Review Checklist
1. Critical & Security
- Security Vulnerabilities: Injection (GraphQL, XSS), insecure data handling, auth flaws.
- Exposed Secrets: No hardcoded API keys, tokens (customerAccessToken, partnerAccessToken), or passwords.
- Input Validation: Validate productId, checkoutId, CEP; sanitize user input before GraphQL.
- Error Handling: Errors caught, handled gracefully; no exposed stack traces or PII.
2. Quality & Best Practices
- DRY: Logic abstracted and reused; no duplicated code.
- SOLID: Single responsibility; dependency injection where appropriate.
- Readability: Consistent naming (camelCase, kebab-case per context); clear variable names; avoid magic numbers.
- TypeScript: Strict types; avoid
any; proper null checks. - Hooks: useCallback for handlers passed to children; useMemo for expensive computations; avoid unnecessary re-renders.
- Wake-specific: Follow patterns from wake-storefront-api, wake-checkout-flow skills.
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.
- yesterday First seen · 117 lines · 28 tokens per session scan A 34fc50ccf4ae
wake-code-reviewer is an agent published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 886 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 agents, from other repositories
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
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…
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…
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.