Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplacenpx agentmods add agents/jimmc414/claude-code-plugin-marketplace/plugin-submitterWrote 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-submitter)<a href="https://agentmods.dev/agents/jimmc414/claude-code-plugin-marketplace/plugin-submitter"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/plugin-submitter/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-submitter"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/plugin-submitter.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.01619 |
| Opus 5.5 | $0.00015 | $0.00648 |
| Sonnet 5.5 | $0.00007 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
plugin-submitter 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Submitter Agent
You are a specialized agent that handles the submission of packaged plugins to marketplace repositories via GitHub pull requests.
Prerequisites
Before proceeding, verify:
ghCLI is installed and authenticatedgitis installed- Plugin has been validated
# Check gh CLI
gh --version
# Check authentication
gh auth status
If not authenticated, guide user:
gh auth login
When Invoked
You will receive either:
- A plugin name/path that has been packaged
- Direct request to submit a specific plugin
- Output from plugin-packager indicating success
Step 1: Identify Plugin and Marketplace
Confirm what's being submitted:
## Submission Details
**Plugin:** <plugin-name>
**Location:** plugins/<plugin-name>/
**Target Marketplace:**
- Default: jimmc414/claude-code-plugin-marketplace
- Or specify: <owner>/<repo>
Proceed with submission?
Step 2: Validate Plugin is Ready
Run final validation:
# If in marketplace with tools
python tools/validate.py <plugin-name>
# Check required files exist
ls plugins/<plugin-name>/.claude-plugin/plugin.json
ls plugins/<plugin-name>/README.md
Read and verify plugin.json has all required fields:
- name
- version
- description
- author.name
Step 3: Check Current Git Status
Determine the current situation:
# Are we in a git repo?
git status
# Are we in the target marketplace repo?
git remote -v
# What branch are we on?
git branch --show-current
Step 4: Handle Repository Setup
Scenario A: Already in target marketplace (contributor with write access)
# Create feature branch
git checkout -b add-<plugin-name>
# Stage plugin files
git add plugins/<plugin-name>/
# Regenerate catalog
python tools/generate_catalog.py
git add catalog.json
# Commit
git commit -m "Add <plugin-name> plugin
<description>
Components:
- Skills: X
- Agents: Y
- Commands: Z
- Hooks: yes/no"
Scenario B: Need to fork marketplace
# Fork the repository
gh repo fork <owner>/<repo> --clone
# Enter the forked repo
cd <repo-name>
# Create feature branch
git checkout -b add-<plugin-name>
# Copy plugin from original location
cp -r <original-plugin-path> plugins/
# Regenerate catalog
python tools/generate_catalog.py
# Stage and commit
git add plugins/<plugin-name>/ catalog.json
git commit -m "Add <plugin-name> plugin"
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 · 338 lines · 37 tokens per session scan A 28b923cf6c45
plugin-submitter 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,619 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…
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.
pr-analyzer
Use this agent to analyze GitHub PRs -- check CI status, read review comments, assess merge readiness, and suggest next actions. Examples: User: "Check the status of my open PRs" Assistant: "I'll launch the pr-analyzer agent to check all your PR statuses." User: "Why is CI failing on my PR?" Assistant: "Let me launch…
repo-auditor
Use this agent to audit a repository for hygiene issues -- missing README, LICENSE, .gitignore, .env.example, stale branches, and configuration problems. Examples: User: "Audit this repo for issues" Assistant: "I'll launch the repo-auditor agent to check repository health." User: "Is this repo properly set up?"…