What is claude-code-plugin?

A Claude Code plugin that connects an application running Vendo to Claude Code through its API. It lets Claude act as the signed-in user while the user's screen displays the interaction.

Use it to let Claude Code perform actions in a Vendo-connected product through generated user interfaces and API calls.

It connects Claude Code to an existing Vendo-based product instead of limiting the agent to text typed in the coding tool.

claude-code-plugin — Plugin by runvendo

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.

Claude Code

/plugin marketplace add runvendo/vendo

agentmods

npx agentmods add plugins/runvendo/vendo/claude-code-plugin

Clone the repo

git clone --depth 1 https://github.com/runvendo/vendo

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

claude-code-plugin 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.

examples/claude-code-plugin/.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "vendo",
  "displayName": "Vendo",
  "description": "Connect Claude Code to a product running Vendo: act through its API as the signed-in user, and make that user a screen instead of typing the answer out.",
  "version": "0.1.0",
  "author": { "name": "Vendo", "url": "https://vendo.run" },
  "homepage": "https://docs.vendo.run/existing-agents/mcp",
  "repository": "https://github.com/runvendo/vendo",
  "license": "Apache-2.0",
  "keywords": ["vendo", "mcp", "generated-ui"]
}

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.

2d ago First seen · 13 lines scan A d40f946860d2

Subscribe to this mod's changes

claude-code-plugin is a plugin published in the GitHub repository runvendo/vendo (594 stars, last pushed 2d ago), 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-08-30.

Backend and APIs Data and AI Frontend agents ai ai-agents automation devtools embedded-ai

claude-code-plugin

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

jenkins-cli

agent-teams

newsjack

moraine

claude-superskills

agents-market