publishing-plugins

publishing-plugins is a skill for Claude Code from jamesgray-ai/handsonai-plugins. It costs 172 tokens per session (5,500 once invoked), scanned A, original, MIT.

A workflow for publishing skills and agents as Claude plugins from one Git repository to another. A Git repository is a project folder whose changes and versions are tracked over time.

In plain words
What is it for?
Use it to copy selected skills and agents into plugin releases for a team, using Git and Bash on the user's computer.
Why use it?
It keeps the source project separate from the plugin repository shared with teammates, reducing the risk of publishing unfinished or unintended changes. It also records release plans and version numbers.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions Claude Code.

Part of the handsonai plugin — 16 skills shipped together

Good fit Use it to copy selected skills and agents into plugin releases for a team, using Git and Bash on the user's computer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jamesgray-ai/handsonai-plugins/publishing-plugins
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.

Any agent
npx skills add jamesgray-ai/handsonai-plugins --skill publishing-plugins
Clone the repo
git clone --depth 1 https://github.com/jamesgray-ai/handsonai-plugins

Made for: Claude Code.

Or install handsonai, the plugin that ships this one along with the rest of its 16 skills.

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 publishing-plugins

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/publishing-plugins/github.svg)](https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/publishing-plugins)
Your own site
<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/publishing-plugins"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/publishing-plugins/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 publishing-plugins

Your own site · 80×15
<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/publishing-plugins"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/publishing-plugins.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 172 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,500 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.00172 $0.05500
Opus 5.5 $0.00069 $0.02200
Sonnet 5.5 $0.00034 $0.01100
Haiku 4.5 $0.00017 $0.00550

Measured 3d ago against content hash cb252c71f2e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

publishing-plugins 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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/publish-plugin.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/handsonai/skills/publishing-plugins/SKILL.md · 311 lines

How it starts

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

Publishing Plugins

Publish skills and agents from the source repository, where they're built and changed, to a separate plugin repository that teammates install in Claude. Skills and agents live once, in the source repository's .claude/skills/ and .claude/agents/. The plugin repository can hold several plugins (one per team, for example), and a release plan in it records which skills and agents go into each plugin, or which are kept just for the user. Nothing reaches a team until someone decides it should, and every release of a plugin gets a new version number.

The script scripts/publish-plugin.sh does the copying, the release plan and the version numbers. It needs Bash and Git on the user's own computer: built into macOS; on Windows, Git for Windows (which brings Git Bash). It runs where Claude works on the user's computer: Claude Code, including the Code tab in the Claude desktop app. If you can't run commands on the user's computer, or git isn't installed, say so plainly and stop: "Publishing needs to run on your own computer. Open the Code tab in the Claude desktop app, choose this folder, and say 'publish my plugin' there." Where bash is missing but git works, follow references/by-hand.md.

The leader never types a path, a Git command or a file name. You find folders, run commands, and play back what you found in plain words for them to confirm.

Workflow

Run the script with bash <this skill's folder>/scripts/publish-plugin.sh <command> --plugin-repo <plugin folder>. Pass paths with forward slashes, on Windows too.

Entry. Find the plugin repository: look in the current folder, then in its parent folder's other folders, for a .publish-plugin file. If one names the current folder (or the folder the user mentioned) as its source=, this is a release:

  1. If the plugin repository has a GitHub connection and GitHub already holds a release (git -C <plugin folder> ls-remote --heads origin prints something), run git -C <plugin folder> pull --ff-only so you start from the latest release. If that fails, show what Git said and stop.
  2. Run list and say in one line what you found (if it marks a version "not yet on GitHub", say that too): "Your source repository is my-ai-work; your plugin repository acme-plugins holds sales-team-skills (version 1.0.2)."
  3. If the user asked to add a plugin or move a skill, do Phase 2 for that. Then go to Phase 3.

Read the full file on GitHub · 311 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago Changed · +42 lines cb252c71f2e6
  2. 4d ago First seen · 269 lines · 172 tokens per session scan A 66c379b6bde9

Subscribe to this mod's changes

publishing-plugins is a skill published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 172 tokens to every session and 5,500 once invoked, about $0.0007 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-11-03.

Related

publishing-plugins compared with skills from other repositories

publishing-plugins next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
publishing-pluginsjamesgray-ai/handsonai-pluginsSkill8yesterdayMITA172Claude Code
release-announcementpaperclipai/paperclipSkill111kyesterdayMITA42Claude Code, Codex
releasethedotmack/claude-memSkill114kyesterdayApache-2.0A13Claude Code
release-notesphuryn/pm-skillsSkill28k8d agoMITA57Claude Code
multi-agent-release-managerchromium/chromiumSkill25kyesterdayBSD-3-ClauseA27Claude Code, Codex
pack-submitaeonfun/aeonSkill788yesterdayMITA27Claude Code, Codex
updater_guidesiddsachar/row-botSkill1.7kyesterdayApache-2.0A22Claude Code, Codex