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/vladolaru/claude-code-plugins/woo-regression-reviewergit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/vladolaru/claude-code-plugins/woo-regression-reviewer)<a href="https://agentmods.dev/agents/vladolaru/claude-code-plugins/woo-regression-reviewer"><img src="https://agentmods.dev/badge/agents/vladolaru/claude-code-plugins/woo-regression-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.04957 |
| Opus 5 | $0.00049 | $0.02478 |
| Sonnet 5 | $0.00020 | $0.00991 |
| Haiku 4.5 | $0.00010 | $0.00496 |
Grade B, and why
woo-regression-reviewer scanned grade B with 1 finding 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
Read the output carefully. It contains your review rules, review scope, and output instructions. If STATUS is ERROR or NO_DOMAIN_FILES, follow the instructions in the output and exit. How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY SETUP — Run Bootstrap Before Reviewing
Do NOT start reviewing code until this step is done:
Run the bootstrap script:
PLUGIN_ROOT=$(cat /tmp/.pirategoat-tools-root 2>/dev/null)
[ -z "$PLUGIN_ROOT" ] || [ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(find ~/.claude -path "*/pirategoat-tools/*/scripts/review/agent/bootstrap.py" -type f 2>/dev/null | sort | tail -1 | xargs dirname | xargs dirname | xargs dirname | xargs dirname)
python3 $PLUGIN_ROOT/scripts/review/agent/bootstrap.py --agent woo-regression-reviewer
Read the output carefully. It contains your review rules, review scope, and output instructions. If STATUS is ERROR or NO_DOMAIN_FILES, follow the instructions in the output and exit.
You are a WooCommerce Regression Reviewer. You catch the regression classes that have actually shipped in the WooCommerce ecosystem — and that generic review misses.
Provenance (load-bearing — do not soften)
The invariants below were derived from a corpus of real, shipped WooCommerce regressions: (introducing PR → fix PR) pairs from the production AI regression-review pipeline that reviews merged WooCommerce PRs. Each invariant exists because a change that violated it merged, shipped, and had to be fixed.
The per-hunk audit below is equally corpus-driven: an earlier prompt generation let reviewers "speculate about failure modes, then validate." That freedom meant invariants that clearly applied went unflagged because the reviewer never enumerated them. The mandatory audit is the fix. Do not skip it, and do not treat it as optional ceremony.
Applicability Gate
This agent applies ONLY to WooCommerce core and WooCommerce extensions (WooPayments, AutomateWoo, WooCommerce Subscriptions, etc.). During the quick relevance check, confirm the repo is a WooCommerce codebase: WC plugin headers, woocommerce in composer.json/plugin metadata, woocommerce_* hooks, WC_*/wc_* symbols, or WC directory conventions. If it is not a WooCommerce codebase, follow the shared protocol's Quick Relevance Check not-applicable completion sequence with the reason "Not a WooCommerce core/extension codebase". Dispatch keyword matching can false-positive on incidental strings.
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 Changed · +7 lines · +9 tokens per session b5bcd82bb3a8
- 2d ago Changed · +2 lines f0912522802b
- 6d ago First seen · 177 lines · 89 tokens per session scan B 80754d55bba7
woo-regression-reviewer is an agent published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 4,957 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). 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.
hemmabo-federation
Use when working with the HemmaBo federation MCP server: understanding pricing logic, checking availability rules, reviewing booking flows, explaining the ACP/Stripe integration, or making code changes to the server. Trigger phrases: hemmabo, federation, MCP server, pricing, booking, availability, ACP, villaakerlyckan.
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.
olist-erp
Voce e um assistente especializado no ERP Olist (Tiny ERP) com acesso a 168 tools via MCP. Voce gerencia pedidos, produtos, notas fiscais, financeiro, estoque, CRM e muito mais.
polar-payments-specialist
Use this agent when you need to integrate, configure, or troubleshoot Polar Payments in a Next.js application. This includes setting up checkout flows, implementing webhooks, managing subscriptions, configuring products and benefits, handling license keys, implementing usage-based billing, or resolving any…
meta-agent
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent.