submit

submit is a command for Claude Code from kossakovsky/cc-plugins. It costs 12 tokens per session (1,326 once invoked), scanned A, original, MIT.

A command that submits a Claude Code plugin to the community marketplace through a pull request. A pull request is a proposed change for project maintainers to review.

In plain words
What is it for?
Use it to validate a plugin, create its marketplace entry, and prepare its submission.
Why use it?
It checks the plugin and stops submission when required files, metadata, documentation, components, or security conditions are missing.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions .claude-plugin; positional $N argument; mentions Claude Code.

Part of the plugin-development plugin — 1 skill, 8 commands, 1 agent, 2 hooks shipped together

Good fit Use it to validate a plugin, create its marketplace entry, and prepare its submission.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kossakovsky/cc-plugins/submit
Install

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.

Clone the repo
git clone --depth 1 https://github.com/kossakovsky/cc-plugins

Made for: Claude Code.

Or install plugin-development, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 1 agent, 2 hooks.

Wrote 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.

agentmods badge for submit

README.md
[![agentmods](https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/submit/github.svg)](https://agentmods.dev/commands/kossakovsky/cc-plugins/submit)
Your own site
<a href="https://agentmods.dev/commands/kossakovsky/cc-plugins/submit"><img src="https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/submit/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.

agentmods 80×15 button for submit

Your own site · 80×15
<a href="https://agentmods.dev/commands/kossakovsky/cc-plugins/submit"><img src="https://agentmods.dev/badge/commands/kossakovsky/cc-plugins/submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01326
Opus 5.5 $0.00005 $0.00530
Sonnet 5.5 $0.00002 $0.00265
Haiku 4.5 $0.00001 $0.00133

Measured 1mo ago against content hash 5636eb8667ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

submit 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.

plugins/plugin-development/commands/submit.md · 183 lines

How it starts

The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Submit Plugin to Marketplace

Guide the user through submitting their plugin to the community marketplace (kossakovsky/cc-plugins).

Arguments

  • $1 (optional): Path to the plugin directory. If not provided, detect from current directory.

Instructions

Step 1: Locate the Plugin

  1. If $1 is provided, use that path
  2. Otherwise, look for .claude-plugin/plugin.json in the current directory or parent directories
  3. If not found, ask the user which plugin to submit

Read the plugin's .claude-plugin/plugin.json and README.md.

Step 2: Validate the Plugin

Run the same checks as /plugin-development:validate:

  • .claude-plugin/plugin.json exists and is valid JSON
  • Required fields present: name (kebab-case), version, description
  • README.md exists with installation and usage sections
  • At least one component directory (commands/, skills/, agents/, or hooks/)
  • No security issues (no hardcoded secrets, no data exfiltration patterns)

If validation fails, show errors and stop. The user must fix issues before submitting.

Step 3: Generate Marketplace Entry

Using data from plugin.json, generate a marketplace entry:

{
  "name": "<from plugin.json>",
  "description": "<from plugin.json>",
  "version": "<from plugin.json>",
  "source": "./plugins/<name>",
  "author": { "name": "<from plugin.json or ask user>" },
  "category": "<ask user to choose>",
  "tags": ["<from plugin.json keywords or ask user>"],
  "keywords": ["<from plugin.json keywords or ask user>"]
}

Available categories: utilities, developer-tools, productivity, ai-tools, integrations.

Show the generated entry to the user for confirmation.

Step 4: Check Prerequisites

Check if gh CLI is available:

gh --version

If gh is available: Offer automated submission (Step 5a). If gh is not available: Provide manual instructions (Step 5b).

Step 5a: Automated Submission (with gh CLI)

Ask the user for confirmation before each step.

Read the full file on GitHub · 183 lines

Changes

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.

  1. 1mo ago First seen · 183 lines · 12 tokens per session scan A 5636eb8667ae

Subscribe to this mod's changes

submit is a command published in the GitHub repository kossakovsky/cc-plugins (3 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 1,326 once invoked, about $0.0000 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-08-31.