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/a8cteam51/claude-code-plugins/wpbakery-batchgit clone --depth 1 https://github.com/a8cteam51/claude-code-pluginsWhat 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.00044 | $0.02894 |
| Opus 5 | $0.00022 | $0.01447 |
| Sonnet 5 | $0.00009 | $0.00579 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
wpbakery-batch 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wpbakery-to-gutenberg:wpbakery-batch
Orchestrate a batch WPBakery→Gutenberg conversion across multiple posts on a local Studio site. Each per-page conversion runs inside a subagent so that the main context window only ever holds the candidate list, the user's choices, and per-page summaries — never the actual post content, rendered HTML, or block markup. This is the only reason this command exists as a command instead of just looping inside the single-page skill.
Per-page work follows the wpbakery-to-gutenberg skill verbatim. Do not reimplement that procedure here — read ${CLAUDE_PLUGIN_ROOT}/skills/wpbakery-to-gutenberg/SKILL.md once at the start so you know what to delegate, then dispatch.
Inputs
$ARGUMENTS— site path (absolute path to the Studio site's WordPress root). Required.
If $ARGUMENTS is empty or doesn't look like an absolute path, ask the user via AskUserQuestion (free-text via "Other").
Step 1 — preconditions (orchestrator-side, run once)
Do these in parallel before any discovery. If any fails, stop with a plain-text reason — no recovery, no workarounds.
command -v studioandstudio --version—studioCLI must be on PATH.studio site status --path=<site-path>— must report a managed site. Capture the Local URL for the report header.- If status reports stopped, run
studio site start --path=<site-path>and wait. studio wp core is-installed --path=<site-path>— must exit 0.- Confirm
mcp__wordpress-studio__validate_blocksis exposed in the current session. If not, surface it: the batch will run, but per-page subagents will skip the validate-and-fix pass and the report will flag every page asvalidate=skipped. mkdir -p <site-path>/.wpbakery-migration/(subagents will stageconverted-<id>.txtandupdate-<id>.phphere, just like the single-page skill).
Step 2 — discover candidates
List every post that contains a WPBakery shortcode marker. Use wp post list --s, not wp db query — on a Studio (SQLite) site $wpdb is not fully loaded under wp db query / wp eval, and raw-SQL paths can return an empty result set even when matching posts exist. wp post list --s runs through WP_Query, which the SQLite integration handles cleanly:
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 · 197 lines · 44 tokens per session scan A b6fd96614c9b
wpbakery-batch is a command published in the GitHub repository a8cteam51/claude-code-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 2,894 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
add-portal
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic linkedin-search and freehire-search), and the README invites users elsewhere to build equivalents — this command turns that invitation…
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
execute
Delegate execution to GJC (runs /skill:ultragoal to completion with verification).
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.