WordPress Playground toolkit for AI agents. Provides skills for spinning up disposable WordPress instances via the Playground CLI (auto-mounting local plugins/themes, switching WP/PHP versions, building snapshots, Xdebug debugging) and for authoring Playground Blueprint JSON files (schema, steps, resources, bundles, common pitfalls). Also provides MCP tools for interacting with a Playground instance running in the browser — managing sites, reading/writing files in the virtual filesystem, executing PHP, making authenticated REST API requests, and navigating pages. Use the CLI skill when you need to mount local project files into WordPress. Use the MCP tools when working with a browser-based Playground instance.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- wp-playground
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
3 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
9 findings · 6.8s
v0.3.74
10 findings · 0.7s
v0.1.0
0 findings · 2.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.7s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 3, 2026 | Flagged74 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Jul 28, 2026 | Flagged75 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 19 findings across every scanner that examined this package.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
1 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/sync-skills.yml · reported by agent-audit-kit
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
4 MANIFEST_MISSING_LICENSE
Files: /repo/wp-playground/skills/wp-playground/SKILL.md, /repo/wp-playground/skills/blueprint/SKILL.md, /repo/SKILL.md and 1 more · reported by cisco-skill-scanner
3 HIDDEN_DATA_FILE
Files: /repo/wp-playground/.codex-plugin/plugin.json, /repo/.agents/plugins/marketplace.json, /repo/.githooks/pre-commit · reported by cisco-skill-scanner
2 AAK-MARKETPLACE-001
Files: .claude-plugin/marketplace.json, .agents/plugins/marketplace.json · reported by agent-audit-kit
2 AAK-MCP-005
Files: .mcp.json, wp-playground/.mcp.json · reported by agent-audit-kit
2 AAK-MCP-007
Files: .mcp.json, wp-playground/.mcp.json · reported by agent-audit-kit
2 AAK-MCP-ATTEST-001
Files: .mcp.json, wp-playground/.mcp.json · reported by agent-audit-kit
2 SOCIAL_ENG_VAGUE_DESCRIPTION
High severity findings in marketplace and supply chain configurations.
The artifact contains high severity findings related to marketplace configuration in `.agents/plugins/marketplace.json` and `.claude-plugin/marketplace.json`. Another high severity finding is present in the supply chain configuration file `.mcp.json`. Additionally, medium severity findings indicate potential issues with attestation and other MCP configurations.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
1 AAK-SUPPLY-001
Files: .mcp.json · reported by agent-audit-kit