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.
git clone --depth 1 https://github.com/zpoint/vibe-sellerWrote 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/plugins/zpoint/vibe-seller/agent)<a href="https://agentmods.dev/plugins/zpoint/vibe-seller/agent"><img src="https://agentmods.dev/badge/plugins/zpoint/vibe-seller/agent/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/plugins/zpoint/vibe-seller/agent"><img src="https://agentmods.dev/badge/plugins/zpoint/vibe-seller/agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibe-seller 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 2d 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.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "vibe-seller",
"displayName": "Vibe Seller",
"version": "0.1.0",
"description": "Drive a Vibe Seller server from your agent: create tasks, follow their progress, answer the agent's questions and review plans over the hosted /api/mcp endpoint.",
"author": {
"name": "Vibe Seller",
"url": "https://github.com/zpoint/vibe-seller"
},
"homepage": "https://github.com/zpoint/vibe-seller",
"repository": "https://github.com/zpoint/vibe-seller",
"license": "Apache-2.0",
"keywords": [
"mcp",
"ecommerce",
"automation",
"amazon",
"vibe-seller"
],
"userConfig": {
"url": {
"type": "string",
"title": "Vibe Seller server URL",
"description": "Base URL of the Vibe Seller server, e.g. http://127.0.0.1:7777 or https://vibe.example.com. No trailing slash, no /api/mcp suffix.",
"required": true
},
"token": {
"type": "string",
"title": "API token",
"description": "Personal access token, minted in Vibe Seller under Settings -> API tokens. Sent as a Bearer token.",
"required": true,
"sensitive": true
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 145 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 37 lines scan A c3f721071e71
vibe-seller is a plugin published in the GitHub repository zpoint/vibe-seller (117 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-06.
vibe-seller compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| vibe-sellerzpoint/vibe-seller | Plugin | 117 | yesterday | Apache-2.0 | A | — | Claude Code |
| shopify-pluginShopify/Shopify-AI-Toolkit | Plugin | 632 | 11d ago | MIT | A | — | Claude Code |
| b2c-cliSalesforceCommerceCloud/b2c-developer-tooling | Plugin | 58 | yesterday | Apache-2.0 | A | — | Claude Code |
| product-sales-analysisdonvito/skillsbento | Plugin | 10 | 2d ago | Apache-2.0 | A | — | Claude Code |
| sap-mmBoxLogoDev/sapstack | Plugin | 20 | 1mo ago | MIT | A | — | Claude Code |
| jpm-payments-skillsjpmorgan-payments/pdp-skills | Plugin | 8 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| verychic-mcpjordantete/verychic-mcp | Plugin | 1 | 12d ago | MIT | A | — | Cursor |