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/cyperx84/claude-code-plugin-examplesWrote 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/cyperx84/claude-code-plugin-examples/productivity-plugin)<a href="https://agentmods.dev/plugins/cyperx84/claude-code-plugin-examples/productivity-plugin"><img src="https://agentmods.dev/badge/plugins/cyperx84/claude-code-plugin-examples/productivity-plugin/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/cyperx84/claude-code-plugin-examples/productivity-plugin"><img src="https://agentmods.dev/badge/plugins/cyperx84/claude-code-plugin-examples/productivity-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
productivity-plugin 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 2mo 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": "productivity-plugin",
"version": "1.5.0",
"description": "Daily productivity tools with standup reports, code reviews, and time tracking",
"author": {
"name": "Claude Code Learning"
},
"keywords": ["productivity", "standup", "review", "intermediate"],
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 37 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.
- 2mo ago First seen · 11 lines scan A d0c873ea2326
productivity-plugin is a plugin published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 1y 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
mattpocock-skills
A collection of coding-agent skills for practical software engineering, including test-driven development, code review, debugging, design, and specification work.
rust-dev
Rust development toolkit with best practices, code review, performance optimization, and async Rust patterns.
aura-gemini
Aura Shell integration for Gemini CLI - native notifications and session status.
quality
Code quality skills — refactoring, naming conventions, project structure, and internationalisation.
code-review
Iterative code review toolkit. Bundles two skills: code-review (diff-based PR review or holistic codebase audit with gap detection and tracked fix loop) and address-pr-review (validate GitHub PR comments, fix, reply, and resolve threads).
electron-playwright-validator
Electron app UI automation and validation via Playwright CDP.