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.
/plugin marketplace add Abdulkader-Safi/wp-to-codenpx agentmods add plugins/abdulkader-safi/wp-to-code/wp-to-codegit clone --depth 1 https://github.com/Abdulkader-Safi/wp-to-codeGrade 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 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.
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 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 · 32 lines scan A beb99466e002
wp-to-code is a plugin published in the GitHub repository Abdulkader-Safi/wp-to-code (2 stars, last pushed 13d 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
figma-console-mcp-skills
Plugin marketplace listing 1 plugin: figma-console-mcp-skills.
ad-video-skills
Plugin marketplace listing 1 plugin: ad-video-skills.
uisandbox
Play with your app's design, right in the browser: open a built web app in UISandbox, 1:1 and with its own knobs, from the chat; try a change, verify, export the patch. Bundles the /uisandbox skill and the uisandbox MCP server.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…
rad-context-prompter
Write, debug, reverse-engineer, and migrate AI prompts — now including agentic loops and goal conditions. The prompt-engineering skill covers writing patterns and platform-specific shape (Claude, GPT, Gemini, Claude Code, OpenAI Codex/AGENTS.md, image generators, agentic tools). The loop-goal-engineering skill authors.
scrollytelling
Turn a video you already have into a complete scroll-scrubbed hero page — Next, Nuxt, Astro or plain HTML. The clip advances frame by frame as the visitor scrolls, with copy beats fading in over it. Measures every frame while encoding it, so the page background matches each frame's own border color and each block of…