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.
git clone --depth 1 https://github.com/Abdulkader-Safi/wp-to-codeWrote 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/plugins/abdulkader-safi/wp-to-code/wp-to-code)<a href="https://agentmods.dev/plugins/abdulkader-safi/wp-to-code/wp-to-code"><img src="https://agentmods.dev/badge/plugins/abdulkader-safi/wp-to-code/wp-to-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/abdulkader-safi/wp-to-code/wp-to-code"><img src="https://agentmods.dev/badge/plugins/abdulkader-safi/wp-to-code/wp-to-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wp-to-code 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 1mo 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
{
"name": "wp-to-code",
"displayName": "WordPress to code",
"version": "0.1.1",
"description": "Port a WordPress site to any stack by measuring the original and diffing rendered geometry.",
"author": {
"name": "Abdulkader Safi",
"email": "[email protected]",
"url": "https://github.com/Abdulkader-Safi"
},
"homepage": "https://github.com/Abdulkader-Safi/wp-to-code",
"repository": "https://github.com/Abdulkader-Safi/wp-to-code",
"license": "MIT",
"keywords": [
"wordpress",
"elementor",
"tailwind",
"migration",
"port",
"laravel",
"nextjs"
],
"userConfig": {
"chrome_path": {
"type": "file",
"title": "Chrome executable",
"description": "Leave blank to autodetect an installed Chrome. Set this only if Chrome lives somewhere unusual.",
"required": false
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 8 commands, 1 hook travel with it, and installing the plugin installs all of them — 241 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 32 lines scan A beb99466e002
wp-to-code is a plugin published in the GitHub repository Abdulkader-Safi/wp-to-code (4 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
designlang
Extract any website's design language and ship it. Fourteen slash commands — /extract, /site, /grade, /battle, /remix, /pack, /theme-swap, /brand, /pair, /studio, /verify, /fidelity, /gallery, /dna — wrap the designlang CLI to pull DTCG tokens, Tailwind/shadcn/Figma vars, motion + voice, synthesize a whole-site…
design-system-ops
Staff-level design system auditing, governance, documentation, validation, and communication — 36 skills, 4 agents, and 13 knowledge notes for the full design system lifecycle.
roast-my-design-system
Roast your repo's design system with real data: a health score, the receipts behind it (every colour, spacing value, duplicated component and inline style), and the first fixes ranked by payoff. Deterministic scanner, benchmarked against 119 public repos and 10 reputable design systems, one shareable light/dark HTML…
notabene
Turnkey docs review: set up notabene on any repo — write the config, create the .notabene store, and start the review server via npx (no toolchain to install) — then run the human↔agent loop: process browser comments on your docs, apply the feedback, mark resolved, write the journal, and verify.
landingforge
A Claude Code engine that manufactures SaaS landing pages to a spec across four axes (conversion, organic SEO, AI-search/GEO, visual craft). Gated specialist phases (strategy -> copy -> design -> build -> discoverability -> conversion QA -> performance) plus a 10-star scoring loop that refuses to ship below a quality…
pm
A bundle for product docs and the tasks that come out of them. Write a spec against a format and verify it before it ships; turn a request thread into a task's context table; file that task in your engineering tracker and keep the two sides reconciled. Where things are stored is decided by config.