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.
/plugin marketplace add ivan-magda/claude-code-plugin-templatenpx agentmods add plugins/ivan-magda/claude-code-plugin-template/plugin-developmentgit clone --depth 1 https://github.com/ivan-magda/claude-code-plugin-templateGrade A, and why
plugin-development 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plugin-development — 100% identical, 2 lines differ
What it actually says
{
"name": "plugin-development",
"version": "1.4.0",
"description": "A comprehensive toolkit for creating, validating, and distributing Claude Code plugins",
"author": {
"name": "Ivan Magda",
"email": "[email protected]",
"url": "https://github.com/ivan-magda"
},
"homepage": "https://github.com/ivan-magda/claude-code-plugin-template",
"repository": "https://github.com/ivan-magda/claude-code-plugin-template",
"license": "MIT",
"keywords": [
"plugin-development",
"plugin-authoring",
"cli-tools",
"validation",
"scaffolding"
]
}
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.
- yesterday First seen · 21 lines scan A e0f46e222e45
plugin-development is a plugin published in the GitHub repository ivan-magda/claude-code-plugin-template (67 stars, last pushed 2mo 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
director-mode-lite
Guidance-first workflows shared by Claude Code, Codex CLI, and Grok Build.
director-mode-lite
Guidance-first Director workflows for Claude Code, Codex CLI, and Grok Build, with portable session relay and native adapters.
tiger-plugins
Plugin marketplace listing 5 plugins: codex-bridge, chat-saver, skill-extractor, update-plugins, lark.
codex-bridge
Bridge OpenAI Codex CLI into Claude Code for cross-model review, verification, task delegation and collaborative generation.
lark
Operate Feishu/Lark (IM, Docs, Base, Sheets, Calendar, Drive, Wiki, Task, OKR, VC, etc.) via the local lark-cli. Mirrors the Claude Code lark skill set for Cowork. 飞书/Lark 全套技能。.
chat-saver
Save, search, manage, and export Claude Code conversations to documents or external platforms.