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/melodic-software/claude-code-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/melodic-software/claude-code-plugins/app-control)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/app-control"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/app-control/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/melodic-software/claude-code-plugins/app-control"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/app-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
app-control 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 today.
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": "app-control",
"version": "0.1.0",
"description": "Launches and operates the project's app, observes it and records evidence, and never judges: /app-control:drive finds the project's own control skill (or falls back to the bundled run skill or a project-type recipe), reports what is reachable with ready, records one artifact with capture, stops only what it started with cleanup, and writes a fixed report.md and report.json that a verifier, a debugger or a CI job reads.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"app-control",
"drive",
"launch",
"evidence",
"capture",
"e2e",
"skill"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 92 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.
- today First seen · 20 lines scan A 672181feecc3
app-control is a plugin published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), 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-10-22.
Other plugins, from other repositories
e2e
E2E test triage, debugging, and fix implementation toolkit.
error-therapist
Audit and rewrite error messages to be helpful and actionable.
quality-tools
Code quality and validation: clone detection, multi-agent E2E validation, performance profiling, schema testing.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.