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/motlin/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/motlin/claude-code-plugins/demo)<a href="https://agentmods.dev/plugins/motlin/claude-code-plugins/demo"><img src="https://agentmods.dev/badge/plugins/motlin/claude-code-plugins/demo/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/motlin/claude-code-plugins/demo"><img src="https://agentmods.dev/badge/plugins/motlin/claude-code-plugins/demo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
demo 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 3d 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
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "demo",
"description": "Demo working software by showing real data crossing real IO boundaries, captured with Showboat and friends rather than written by hand, then delivered where the user actually is",
"version": "1.37.0",
"license": "Apache-2.0",
"author": {
"name": "Craig Motlin"
},
"skills": ["./skills/demo"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 107 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.
- 3d ago Changed 26f7a1718fd1
- 6d ago Changed 2741e6f7386b
- 9d ago Changed c96e3dd28189
- 29d ago Changed 8499e9f01461
- 1mo ago Changed · -1 lines 1192763f7d24
- 1mo ago Changed 00a6e97fa6a3
- 1mo ago Changed b04529035dd6
- 1mo ago First seen · 13 lines scan A 2f3cb0509352
demo is a plugin published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. 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-09-07.
Other plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
code-modernization
Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page…