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/johnkozaris/jko-claude-pluginsWrote 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/johnkozaris/jko-claude-plugins/electron-playwright-validator)<a href="https://agentmods.dev/plugins/johnkozaris/jko-claude-plugins/electron-playwright-validator"><img src="https://agentmods.dev/badge/plugins/johnkozaris/jko-claude-plugins/electron-playwright-validator/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/johnkozaris/jko-claude-plugins/electron-playwright-validator"><img src="https://agentmods.dev/badge/plugins/johnkozaris/jko-claude-plugins/electron-playwright-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
electron-playwright-validator 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": "electron-playwright-validator",
"description": "Electron app UI automation and validation via Playwright CDP",
"version": "1.4.0",
"license": "MIT",
"author": {
"name": "John Kozaris"
},
"homepage": "https://github.com/johnkozaris/jko-claude-plugins",
"repository": "https://github.com/johnkozaris/jko-claude-plugins",
"keywords": [
"electron",
"playwright",
"automation",
"validation",
"e2e",
"cdp",
"accessibility"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 90 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 · 21 lines scan A 891de2f6b02f
electron-playwright-validator is a plugin published in the GitHub repository johnkozaris/jko-claude-plugins (11 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-30.
Other plugins, from other repositories
dotnet-backend
Pure .NET 10 backend architecture for Kestrel-hosted REST and SignalR services with DI, data access, and SOLID review.
esp32-cpp
ESP32 firmware review for all variants, FreeRTOS, ESP-IDF/PlatformIO, peripherals, and memory.
python-backend
Python backend architecture for Litestar and FastAPI with SQLAlchemy and SOLID patterns.
rust
Rust code critique, architecture guidance, and idiomatic pattern enforcement.
dead-code
Find and remove dead code, unused imports, and duplicates across any language.
swiftui
SwiftUI patterns and critique for iOS, macOS, and visionOS apps.