A command that adds a skill from skills.sh, a directory of reusable coding-agent skills, to a marketplace plugin. It takes a plugin name, a GitHub repository URL, and optionally the names of specific skills.

It helps package one or more skills from a GitHub repository as a marketplace plugin using the `/add-skill` command.

It avoids manually copying skill files and configures the plugin to use the selected repository skills.

add-skill — Command by pleaseai

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.

agentmods

npx agentmods add commands/pleaseai/claude-code-plugins/add-skill

Clone the repo

git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Per session 44 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,775 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00044	$0.01775
Opus 5	$0.00022	$0.00888
Sonnet 5	$0.00009	$0.00355
Haiku 4.5	$0.00004	$0.00178

Measured yesterday against content hash bd491f137c69, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-skill 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 yesterday.

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.

.claude/commands/add-skill.md · 199 lines

How it starts

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

Add a skills.sh skill as a plugin to the marketplace.

Arguments: $ARGUMENTS (format: <plugin-name> <github-repo-url> [--skill <skill-name> [<skill-name2> ...]])

Examples:

/add-skill slack-agent https://github.com/vercel-labs/slack-agent-skill
/add-skill slack-agent https://github.com/vercel-labs/slack-agent-skill --skill slack-agent
/add-skill agent-skills https://github.com/vercel-labs/agent-skills --skill pr-review commit

Step 1 — Parse & Validate Input

Parse $ARGUMENTS to extract:

PLUGIN_NAME: first token (e.g. agent-skills)
REPO_URL: second token (e.g. https://github.com/vercel-labs/agent-skills)
SKILL_NAMES: all space-separated values after --skill flag until the end of arguments (e.g. pr-review commit → ["pr-review", "commit"]). Defaults to [PLUGIN_NAME] if --skill is not provided.
OWNER_REPO: short form of the URL (e.g. vercel-labs/agent-skills)

Validate:

Both PLUGIN_NAME and REPO_URL are present. If not, stop and show:

Usage: /add-skill <plugin-name> <github-repo-url> [--skill <skill-name> [<skill-name2> ...]]

REPO_URL matches https://github.com/<owner>/<repo>. Normalize to <owner>/<repo> short form.
PLUGIN_NAME contains only alphanumeric characters, hyphens, and underscores.
Each name in SKILL_NAMES contains only alphanumeric characters, hyphens, and underscores.

Check for conflicts:

plugins/<PLUGIN_NAME>/ must NOT already exist
PLUGIN_NAME must NOT already be in .claude-plugin/marketplace.json

If either check fails, stop and report the conflict.

Step 2 — Install Skills inside Plugin Directory

Create the plugin directory and install each skill into it. Run the following for each name in SKILL_NAMES:

mkdir -p plugins/<PLUGIN_NAME>
(cd plugins/<PLUGIN_NAME> && bunx skills add <OWNER_REPO> --skill <SKILL_NAME> --agent 'universal' -y)

bunx skills add run from plugins/<PLUGIN_NAME>/ will:

Install skill files to plugins/<PLUGIN_NAME>/.agents/skills/<SKILL_NAME>/
Append to (or create) plugins/<PLUGIN_NAME>/skills-lock.json scoped to this plugin

Read the full file on GitHub · 199 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.

yesterday First seen · 199 lines · 44 tokens per session scan A bd491f137c69

Subscribe to this mod's changes

add-skill is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 7d ago), licensed MIT. It adds 44 tokens to every session and 1,775 once invoked, about $0.0002 per session on Opus 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-30.

add-skill

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Step 1 — Parse & Validate Input

Step 2 — Install Skills inside Plugin Directory

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement