Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yojahny55/claude-wp-builder/plugin install claude-wp-builderWrote 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/commands/yojahny55/claude-wp-builder/wp-clone)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-clone"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-clone.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.00013 | $0.02600 |
| Opus 5 | $0.00006 | $0.01300 |
| Sonnet 5 | $0.00003 | $0.00520 |
| Haiku 4.5 | $0.00001 | $0.00260 |
Grade A, and why
wp-clone scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bash -c "curl -sI -o /dev/null -w '%{http_code}' https://local-clone.local.com/ 2>/dev/null || echo 'Could not reach site'" How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WP Clone — Remote/Staging Site Cloning
Clone an existing WordPress site into a local development environment. Supports two paths: automated SSH-based cloning or manual import from SQL dump + uploads archive.
Step 0: Parse Arguments
Parse $ARGUMENTS for the following flags:
| Flag | Required | Description |
|---|---|---|
--from= |
Path A only | SSH URL: ssh://user@host/path/to/wordpress |
--to= |
Yes | Local destination path (e.g., /var/www/html/local-clone) |
--sql= |
Path B only | Path to a SQL dump file (e.g., /tmp/dump.sql) |
--uploads= |
Path B only | Path to uploads zip/tar archive (e.g., /tmp/uploads.zip) |
Parsing rules:
- If
--from=starts withssh://, extractuser,host, andremote_pathfromssh://user@host/path. - If
--to=is missing, ask the user for a local destination path. - If neither
--from=nor--sql=is provided, ask the user which path they want:"How would you like to clone? A) SSH — automated pull from a remote server B) Manual — import from a SQL dump file + uploads archive"
Step 1: Determine Clone Path
| Condition | Path |
|---|---|
--from=ssh://... is provided |
Path A — SSH Automated |
--sql= is provided |
Path B — Manual Import |
| Neither provided | Ask user (see Step 0) |
Path A — SSH Automated Clone
A1: Check Prerequisites
Verify that ssh, scp, and rsync are available locally:
bash -c "command -v ssh && command -v scp && command -v rsync"
If any tool is missing, abort with a clear message:
"Missing required tool:
<tool>. Install it before running SSH clone."
A2: Verify SSH Connectivity
Test that the SSH connection works and that the remote path exists:
bash -c "ssh -o ConnectTimeout=10 -o BatchMode=yes user@host 'test -d /remote/path && echo OK'"
If this fails, inform the user:
"Cannot connect via SSH. Check that:
- SSH key is configured for user@host
- The remote path exists
- The user has read access to the WordPress directory"
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.
- 6d ago First seen · 341 lines · 13 tokens per session scan A 45639136eadd
wp-clone is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 2,600 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
debug-helper
Use when something is broken and you need it diagnosed. A build failure, a runtime crash, a blank page, an unreadable error message, or behaviour that is simply wrong. Gives one exact fix, not a list of things to try.