publish-skill

publish-skill is a skill for Claude Code from pengguanya/claude-toolkit. It costs 17 tokens per session (2,673 once invoked), scanned C, original, MIT.

A workflow for moving skills between a private skills folder and a public toolkit repository.

In plain words
What is it for?
Promoting, copying, forking, or adopting skills between private and public repositories.
Why use it?
It manages the paths and configuration needed to share or adopt skills without manually coordinating the two locations.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Good fit Promoting, copying, forking, or adopting skills between private and public repositories.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pengguanya/claude-toolkit/publish-skill
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 pengguanya/claude-toolkit --skill publish-skill
Clone the repo
git clone --depth 1 https://github.com/pengguanya/claude-toolkit

Made for: Claude Code.

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-skill

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/pengguanya/claude-toolkit/publish-skill"><img src="https://agentmods.dev/badge/skills/pengguanya/claude-toolkit/publish-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,673 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00017 $0.02673
Opus 5 $0.00009 $0.01337
Sonnet 5 $0.00003 $0.00535
Haiku 4.5 $0.00002 $0.00267

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

Security

Grade C, and why

publish-skill scanned grade C with 1 finding 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 10d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf $SKILLS_DIR/<name>
skills/publish-skill/SKILL.md · 282 lines

How it starts

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

Publish Skill

Manage skills between a private skills directory and a public toolkit repo.

Configuration

This skill stores its configuration in a JSON file next to this SKILL.md:

<skill-base-dir>/config.json

The config file contains:

{
  "SKILLS_DIR": "~/.claude/skills",
  "TOOLKIT_DIR": "~/path/to/your/toolkit",
  "TOOLKIT_SKILLS": "~/path/to/your/toolkit/skills"
}

First-run setup

Before executing ANY workflow, check if config.json exists in this skill's directory. If it does NOT exist:

  1. Tell the user: "This is your first time running publish-skill. I need to know where your toolkit repo and skills directory are."
  2. Ask for SKILLS_DIR — "Where are your Claude Code skills stored?" (default: ~/.claude/skills)
  3. Ask for TOOLKIT_DIR — "Where is your public toolkit git repo?" (no default — user must provide this)
  4. Set TOOLKIT_SKILLS to $TOOLKIT_DIR/skills and confirm with user
  5. Write the config to config.json next to this SKILL.md
  6. Continue with the requested workflow

If config.json exists, read it and use those values for all paths below.

All commands below use $SKILLS_DIR, $TOOLKIT_DIR, and $TOOLKIT_SKILLS — substitute the values from config.json.

Arguments

$ARGUMENTS

Input Action
promote <skill-name> Move private skill to public toolkit, replace local with symlink
fork <skill-name> [--public-name <name>] Create generalized public copy, keep private version
adopt <skill-name-or-url> Install public skill and customize as private
status Show which skills are private, public, or symlinked
diff <skill-name> For forked skills: show diff between private and public versions
Empty or help Explain available modes

Workflow: Status

Run this first to understand the current state.

# List all skills and their status
for dir in $SKILLS_DIR/*/; do
  name=$(basename "$dir")
  if [ -L "${dir%/}" ]; then
    target=$(readlink -f "${dir%/}")
    echo "SYMLINKED  $name -> $target"
  elif [ -d $TOOLKIT_SKILLS/"$name" ]; then
    echo "FORKED     $name (private + public versions)"
  else
    echo "PRIVATE    $name"
  fi
done

# Show public skills not installed locally
for dir in $TOOLKIT_SKILLS/*/; do
  name=$(basename "$dir")
  [ -e $SKILLS_DIR/"$name" ] || echo "PUBLIC_ONLY $name (not installed locally)"
done

Read the full file on GitHub · 282 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. 10d ago First seen · 282 lines · 17 tokens per session scan C f3301adbafe0

Subscribe to this mod's changes

publish-skill is a skill published in the GitHub repository pengguanya/claude-toolkit (2 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 2,673 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens