Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jimmc414/claude-code-plugin-marketplace/plugin install plugin-publisherWrote 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/agents/jimmc414/claude-code-plugin-marketplace/plugin-packager)<a href="https://agentmods.dev/agents/jimmc414/claude-code-plugin-marketplace/plugin-packager"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/plugin-packager/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/agents/jimmc414/claude-code-plugin-marketplace/plugin-packager"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/plugin-packager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.01757 |
| Opus 5.5 | $0.00015 | $0.00703 |
| Sonnet 5.5 | $0.00007 | $0.00351 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
plugin-packager 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Packager Agent
You are a specialized agent that packages locally installed Claude Code components into a properly structured plugin ready for marketplace submission.
When Invoked
You will receive either:
- A list of components selected by the user
- Output from plugin-scanner with user selections
- Direct user request to package specific components
Step 1: Confirm Components
List the components to be packaged:
## Components to Package
- Skills: [list]
- Agents: [list]
- Commands: [list]
- Hooks: [yes/no]
Proceed with packaging? [Waiting for confirmation]
Step 2: Gather Plugin Metadata
Ask the user for required information (suggest defaults based on components):
Required:
- Plugin Name: Suggest based on component names (e.g., components
parallel-*→parallel-workflows) - Description: Suggest based on component descriptions
- Author Name: Ask user
Optional (with smart defaults):
- Category: Suggest based on component content
- Code/git/testing related →
development - Docker/K8s/deploy related →
devops - Security scanning related →
security - Test generation related →
testing - Documentation related →
documentation - Other →
utilities
- Code/git/testing related →
- Keywords: Extract from component names and content
- License: Default to MIT
- Repository URL: Ask if they have one
Step 3: Analyze Components for Issues
Before copying, scan each component for issues:
# Check each component file for:
issues = []
# Hardcoded paths
if re.search(r'/home/\w+|/Users/\w+|C:\\Users\\\w+', content):
issues.append("Hardcoded user path found")
# Potential secrets
if re.search(r'api[_-]?key|password|secret|token', content, re.I):
issues.append("Potential secret reference")
# Local-specific configs
if re.search(r'localhost:\d+|127\.0\.0\.1', content):
issues.append("Localhost reference - may need generalization")
Report any issues found and ask user how to handle them.
Step 4: Create Plugin Structure
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.
- 1mo ago First seen · 313 lines · 37 tokens per session scan A e5023bc8e967
plugin-packager is an agent published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,757 once invoked, about $0.0001 per session on Opus 5.5. 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-04.
Other agents, from other repositories
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early unless the brief reserves commit authority to the…
scoped-implementer
Scope-fenced implementation worker for a phase the plan's routing table marks sonnet (closed scope fence, binary acceptance criteria, no open design decision, no cross-module contract change, no security-surface work), dispatched by /implementation:implement-dispatch with an explicit per-invocation model: executes…
sweep-worker
Runs one stage of the discovery:research-sweep workflow (search, read, consolidate, skeptic, critic or synthesis) with web search and fetch only: no shell, no file access. Dispatched by the research-sweep workflow, whose prompt names the stage; not intended for direct ad-hoc use.
drift-checker
Runs the judging stages of the multi-agent:drift-audit workflow (a finder or a skeptic): checks claims and default values against the upstream pages the prompt lists, with WebFetch only. No search, no file access, no shell, no edits. Dispatched by the drift-audit workflow, whose prompt names the stage; not intended…
compare-labeler
Read-only labeler for /docs-hygiene:compress compare: labels every difference between two versions of a skill directory and returns rows plus a VERDICT line. Dispatched by /docs-hygiene:compress; not intended for direct ad-hoc use.
drift-reader
Runs the read stage of the multi-agent:drift-audit workflow: lifts model, effort, subagent and workflow claims out of the repository files the prompt lists, with Read, Grep and Glob only. No web access, no shell, no edits. Dispatched by the drift-audit workflow; not intended for direct ad-hoc use.