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 YoungjaeDev/my-claude-pluginsnpx agentmods add plugins/youngjaedev/my-claude-plugins/devgit clone --depth 1 https://github.com/YoungjaeDev/my-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/youngjaedev/my-claude-plugins/dev)<a href="https://agentmods.dev/plugins/youngjaedev/my-claude-plugins/dev"><img src="https://agentmods.dev/badge/plugins/youngjaedev/my-claude-plugins/dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
dev 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": "dev",
"version": "1.0.0",
"description": "Development lifecycle in one bundle. GitHub workflow — commit-and-push, decompose-issue, resolve-issue, release, cr-fix (unified CodeRabbit + ChatGPT-Codex review loop with autonomous apply/defer/skip judgment and rate-limit fallback), post-merge (branch cleanup + config/wiki integration with a mandatory wiki-lore ingest), state-tracker (spec/issue/PR aggregate over .claude/state/spec.json). Project setup — new (first-day bootstrap: interview, .claude/ scaffold, CLAUDE.md + AGENTS.md with Codex reviewer guidelines, gh repo create) and wiring (14-axis harness diagnostic for an existing repo, read-only until approved). Playwright E2E harness — e2e-setup, e2e-author, e2e-debug wrap Playwright's planner/generator/healer agents; never overwrite an existing playwright.config and degrade gracefully without Playwright.",
"skills": [
"./skills/commit-and-push",
"./skills/decompose-issue",
"./skills/resolve-issue",
"./skills/release",
"./skills/cr-fix",
"./skills/post-merge",
"./skills/state-tracker",
"./skills/new",
"./skills/wiring",
"./skills/e2e-setup",
"./skills/e2e-author",
"./skills/e2e-debug"
]
}
What it installs
The manifest is a name and a version. 12 skills travel with it, and installing the plugin installs all of them — 1,774 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill cr-fix A 156 tokens
- Skill e2e-author A 150 tokens
- Skill e2e-debug A 160 tokens
- Skill new A 167 tokens
- Skill release A 127 tokens
- Skill commit-and-push A 107 tokens
- Skill post-merge B 167 tokens
- Skill resolve-issue B 166 tokens
- Skill wiring B 147 tokens
- Skill decompose-issue B 192 tokens
- Skill e2e-setup B 155 tokens
- Skill state-tracker B 80 tokens
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 7e9910828abf
dev is a plugin published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed yesterday), 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-09-05.
Other plugins, from other repositories
utility-tools
Developer productivity tools for Claude Code — generate McKinsey-style HTML slide decks from marketing strategies, automate software releases with version bumping, changelog generation, git tagging, and GitHub release publishing. 3 skills for teams shipping fast.
accessibility-test-scanner
A11y compliance testing with WCAG 2.1/2.2 validation, screen reader compatibility, and automated accessibility audits.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
pr-tools
Safe git push and PR workflow skill that prevents pushing to merged or closed PRs.
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.