Borrowing it
Nothing to install: this file belongs to datathings/marketplace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/datathings/marketplace/main/.claude/commands/add_new_skill.mdgit clone --depth 1 https://github.com/datathings/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/datathings/marketplace/add_new_skill)<a href="https://agentmods.dev/commands/datathings/marketplace/add_new_skill"><img src="https://agentmods.dev/badge/commands/datathings/marketplace/add_new_skill.svg" alt="Measured on agentmods" 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.04092 |
| Opus 5 | $0.00000 | $0.02046 |
| Sonnet 5 | $0.00000 | $0.00818 |
| Haiku 4.5 | $0.00000 | $0.00409 |
Grade C, and why
add_new_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 7d 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 "plugins/$SKILL_NAME/skills/$SKILL_NAME/scripts" How it starts
The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add New Skill to Marketplace
This command adds a new skill plugin to the marketplace from a git repository.
Start by asking the user for the two required inputs below, then execute all steps.
Required Inputs
Ask the user for both before starting:
- Git repository URL - the upstream library/project repo (e.g.,
https://github.com/org/my-lib) - Skill name - hyphen-case identifier matching the directory name (e.g.,
my-lib)
Optionally ask for a specific tag/version to checkout (default: latest tag, or main/master if no tags exist).
Plugin Structure to Create
plugins/<skill-name>/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest
├── skills/<skill-name>/
│ ├── SKILL.md # Main skill entry point
│ └── references/ # Detailed docs loaded on-demand
│ ├── api-*.md # API sections (split by domain)
│ └── workflows.md # Working examples
├── <repo-dir>/ # Standalone git clone (gitignored)
│ └── .git/
└── .gitignore # Ignores *.skill and <repo-dir>/
Process
Subagent strategy: Steps 4 and 5 (repository analysis + skill content generation) are context-heavy and must be dispatched to subagents using the
Tasktool. Run steps 1–3 in the main context, then hand off to subagents for the exploration and writing work, then return to main context for steps 6–11.
1. Create Plugin Directory Structure
SKILL_NAME="<skill-name>"
PLUGIN_DIR="plugins/$SKILL_NAME"
mkdir -p "$PLUGIN_DIR/.claude-plugin"
mkdir -p "$PLUGIN_DIR/skills/$SKILL_NAME/references"
2. Clone the Git Repository
cd "plugins/$SKILL_NAME"
# Clone the upstream repo
git clone <repo-url> <repo-dir>
cd <repo-dir>
# Checkout latest stable tag if available
LATEST_TAG=$(git tag --sort=-version:refname | head -n 1)
if [ -n "$LATEST_TAG" ]; then
echo "Checking out latest tag: $LATEST_TAG"
git checkout "$LATEST_TAG"
else
echo "No tags found, staying on default branch: $(git branch --show-current)"
fi
# Record the version for documentation
CURRENT_VERSION=$(git describe --tags --abbrev=0 2>/dev/null || git rev-parse --short HEAD)
echo "Version: $CURRENT_VERSION"
cd ../../..
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.
- 7d ago First seen · 496 lines · 0 tokens per session scan C 427a376b6c95
add_new_skill is a command published in the GitHub repository datathings/marketplace (11 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,092 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.