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.
/plugin marketplace add barnburner121/claude-plugin-marketplacenpx agentmods add plugins/barnburner121/claude-plugin-marketplace/api-forgegit clone --depth 1 https://github.com/barnburner121/claude-plugin-marketplaceGrade A, and why
api-forge 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 0 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 · 9 lines scan A 37e14a505876
api-forge is a plugin published in the GitHub repository barnburner121/claude-plugin-marketplace (3 stars, last pushed 5mo ago), with no licence file. 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-31.
Other plugins, from other repositories
rudder-core
Cross-tool RudderStack domain knowledge: data catalog, data graphs, tracking plans, instrumentation planning, instrumentation debugging, and destination delivery debugging.
rudder-mcp
Workflows for RudderStack's MCP server at mcp.rudderstack.com: connect AI/LLM agents to a RudderStack workspace and drive catalog, sources, destinations, transformations, RETL, tracking plans, and live events via MCP tool calls.
rudder-profiles
Workflows for building and maintaining RudderStack Profiles projects: setup, project creation, analysis, updates, and debugging.
rudder-terraform
Workflows for managing RudderStack workspaces with the Terraform provider: provider setup, resource and data-source usage, init/plan/apply cycles, module structure, and state management.
rudder-cli
Workflows for driving the rudder-cli and rudder-typer CLIs: validate, dry-run, apply, import, transformations.
canvas-to-code-marketplace
Single-plugin marketplace for Canvas-to-Code — translates canvas designs (HTML + screenshot) into design-system-aligned code through eleven explicit gates.