publish

publish is a command for Claude Code from claude-market/marketplace. It costs 0 tokens per session (1,473 once invoked), scanned A, original, MIT.

A command for publishing a Claude Code plugin to the Claude Market marketplace. It checks changed plugins, validates them, creates marketplace metadata, makes a semantic commit, and opens a pull request.

In plain words
What is it for?
Use it to detect modified plugins, create a release branch when needed, generate marketplace manifests, commit the changes, and submit them for review.
Why use it?
It organizes the release process and reduces the chance of publishing the wrong plugin or missing marketplace files.

Command for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: mentions subagents; mentions Claude Code.

Part of the plugin-builder plugin — 5 commands shipped together

Good fit Use it to detect modified plugins, create a release branch when needed, generate marketplace manifests, commit the changes, and submit them for review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/claude-market/marketplace/publish
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/claude-market/marketplace

Made for: Claude Code.

Or install plugin-builder, the plugin that ships this one along with the rest of its 5 commands.

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 publish

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/claude-market/marketplace/publish"><img src="https://agentmods.dev/badge/commands/claude-market/marketplace/publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,473 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.00000 $0.01473
Opus 5 $0.00000 $0.00737
Sonnet 5 $0.00000 $0.00295
Haiku 4.5 $0.00000 $0.00147

Measured 11d ago against content hash e0444002f7e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

publish 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 11d 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.

plugin-builder/commands/publish.md · 202 lines

How it starts

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

Publish Command

You are helping publish a Claude Code plugin to the Claude Market marketplace.

Overview

This command validates changed plugins, generates the marketplace manifest, creates a semantic commit, and opens a pull request to the marketplace repository.

Step 1: Identify Changed Plugins

Check the current branch with git branch --show-current.

If on main branch:

  • Run git status --porcelain to find uncommitted/staged changes
  • Parse the output to identify which plugins have been modified

If on a different branch:

  • Run git diff main --name-only to find all changed files compared to main
  • Parse the output to identify which plugins have been modified

Look for paths matching {plugin-name}/.claude-plugin/plugin.json or {plugin-name}/*.

Extract the unique plugin names from the changed paths.

If no plugin changes are detected, inform the user and exit.

Step 2: Branch Management

Check the current branch (already checked in Step 1).

If on main branch:

  • Attempt to get GitHub username with git config user.github || git config user.name
  • Create branch name in format: {github-user}/{plugin-affected}/{very-short-description}
    • Use kebab-case for all parts
    • Keep description to 3-4 words max
    • Example: danielkov/browser-tools/add-chromium-mcp
  • Run git checkout -b {branch-name} to create and switch to new branch
  • Note: Do not stage or commit yet - changes will be committed after validation passes

If on a different branch (not main):

  • Continue with the existing branch
  • Note: Do not stage or commit yet - changes will be committed after validation passes

Step 3: Validate Changed Plugins in Parallel

For each changed plugin identified in Step 1, spawn a sub-agent using the Task tool to validate the plugin.

Use a single message with multiple Task tool calls to validate all plugins simultaneously:

For each plugin, spawn an agent with:
- subagent_type: "general-purpose"
- model: "haiku" (for speed)
- description: "Validate {plugin-name}"
- prompt: "Run the command `/plugin-builder:validate {plugin-name} --minimal` and return ONLY the exit code and output. The output should start with either '0' (success) or '1' (failure) followed by any error details."

Read the full file on GitHub · 202 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. 11d ago First seen · 202 lines · 0 tokens per session scan A e0444002f7e5

Subscribe to this mod's changes

publish is a command published in the GitHub repository claude-market/marketplace (23 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,473 tokens. 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.