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.
git clone --depth 1 https://github.com/claude-market/marketplaceWrote 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/commands/claude-market/marketplace/publish)<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.
<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>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.00000 | $0.01473 |
| Opus 5 | $0.00000 | $0.00737 |
| Sonnet 5 | $0.00000 | $0.00295 |
| Haiku 4.5 | $0.00000 | $0.00147 |
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.
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 --porcelainto find uncommitted/staged changes - Parse the output to identify which plugins have been modified
If on a different branch:
- Run
git diff main --name-onlyto 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."
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.
- 11d ago First seen · 202 lines · 0 tokens per session scan A e0444002f7e5
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.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ship
Deploy feature through automated staging validation to production with rollback testing.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.