Borrowing it
Nothing to install: this file belongs to pleaseai/claude-code-plugins. 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/pleaseai/claude-code-plugins/main/.claude/commands/add-vendor.mdgit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote 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/pleaseai/claude-code-plugins/add-vendor)<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/add-vendor"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/add-vendor/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/pleaseai/claude-code-plugins/add-vendor"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/add-vendor.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.01836 |
| Opus 5.5 | $0.00000 | $0.00734 |
| Sonnet 5.5 | $0.00000 | $0.00367 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
add-vendor 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 1mo 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a new Type 2 vendor to the marketplace.
Arguments: $ARGUMENTS (format: <vendor-name> <github-repo-url>)
Example: /add-vendor mastra https://github.com/mastra-ai/skills
Step 1 — Parse & Validate Input
Parse $ARGUMENTS to extract:
VENDOR_NAME: first token (e.g.oxc)REPO_URL: second token (e.g.https://github.com/nicolo-ribaudo/oxc)
Validate:
- Both tokens are present. If not, stop and show:
Usage: /add-vendor <name> <github-repo-url> REPO_URLmatches patternhttps://github.com/<owner>/<repo>(or[email protected]:<owner>/<repo>). Normalize to HTTPS form.VENDOR_NAMEcontains only alphanumeric characters, hyphens, and underscores.
Check scripts/meta.ts — read the file and verify VENDOR_NAME is NOT already a key in the vendors object. If it already exists, stop and report: Vendor '<name>' already exists in scripts/meta.ts.
Step 2 — Explore Vendor Repository
Use the GitHub MCP tool or gh CLI to browse the vendor repository and find its skills/ directory:
gh api repos/<owner>/<repo>/contents/skills
- If the API returns a 404 or the directory doesn't exist, stop and report:
No skills/ directory found in <REPO_URL>. This repository is not a Type 2 vendor (it doesn't self-host skills). Consider using /generate-skill for Type 1 skill generation from docs. - If the directory exists, list all subdirectory names under
skills/— these are the available source skills.
Display the found skills to the user:
Found skills in <REPO_URL>/skills/:
- <skill-1>
- <skill-2>
...
Step 3 — Determine Skill → Plugin Mappings
For each skill found, determine:
- Output skill name — usually the same as the source skill name (identity mapping). Ask the user if they want to rename any skill.
- Target plugin — which
plugins/<plugin>/directory the skill should go into.
Read scripts/cli.ts to see existing SKILL_TO_PLUGIN entries and existing plugins in plugins/.
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.
- 1mo ago First seen · 229 lines · 0 tokens per session scan A 1f08251d85d5
add-vendor is a command published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,836 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
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.