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/mathisk2095/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/mathisk2095/jko-claude-plugins/dead-code)<a href="https://agentmods.dev/plugins/mathisk2095/jko-claude-plugins/dead-code"><img src="https://agentmods.dev/badge/plugins/mathisk2095/jko-claude-plugins/dead-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/mathisk2095/jko-claude-plugins/dead-code"><img src="https://agentmods.dev/badge/plugins/mathisk2095/jko-claude-plugins/dead-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dead-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": "dead-code",
"description": "Find and remove dead code, unused imports, and duplicates across any language",
"version": "1.0.0",
"license": "MIT",
"author": {
"name": "John Kozaris"
},
"homepage": "https://github.com/johnkozaris/jko-claude-plugins",
"repository": "https://github.com/johnkozaris/jko-claude-plugins",
"keywords": [
"dead-code",
"unused",
"cleanup",
"simplify",
"duplicate",
"DRY",
"imports",
"refactoring",
"lint",
"code-quality"
]
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands travel with it, and installing the plugin installs all of them — 164 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 · 24 lines scan A 94621dee8df3
dead-code is a plugin published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 3d 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
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.
esp32-cpp
Evidence-first ESP32 firmware guidance for hardware, FreeRTOS, memory, peripherals, and field failures.
backend-architecture
Small, opinionated architecture guide for production backend services across languages and frameworks.
backend-validator
Backend API and WebSocket validation via Hurl, websocat, and oauth2c with OIDC token caching.
electron-playwright-validator
Electron app UI automation and validation via Playwright CDP.
maestro-mobile-validator
iOS and Android mobile app validation via Maestro flows with simulator management and CI patterns.