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 pinecone-io/pinecone-claude-code-pluginnpx agentmods add plugins/pinecone-io/pinecone-claude-code-plugin/marketplacegit clone --depth 1 https://github.com/pinecone-io/pinecone-claude-code-pluginGrade A, and why
pinecone-plugins 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
{
"name": "pinecone-plugins",
"owner": {
"name": "Pinecone"
},
"plugins": [
{
"name": "pinecone",
"source": "./",
"description": "Pinecone vector database integration. Streamline your Pinecone development with powerful tools for managing vector indexes, querying data, and rapid prototyping. Use slash commands like /quickstart to learn Pinecone and initialize Python projects and /query to quickly explore indexes. Access the Pinecone MCP server for creating, describing, upserting and querying indexes with Claude. Perfect for developers building semantic search, RAG applications, recommendation systems, and other vector-based applications with Pinecone."
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 14 lines scan A 1820c2e5c3e5
pinecone-plugins is a plugin published in the GitHub repository pinecone-io/pinecone-claude-code-plugin (68 stars, last pushed 18d ago), licensed MIT. 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.
Other plugins, from other repositories
lex
UK legal research skill for Claude Code using the Lex API.
lean-explore
Plugins for searching Lean 4 declarations with LeanExplore.
codealive-marketplace
Plugin marketplace listing 1 plugin: codealive.
grounded-forge
A retrieval architecture that pre-projects sources to task domains at ingestion time. Runtime becomes lookup, not reshape. Ships skills for ingesting sources under a 9-pass source-only protocol, retrieving via two-layer indexes (corpus catalogue + per-task distillation indexes), and a PreToolUse hook that enforces…
session-recall-marketplace
Local shared-memory plugin for Claude Code, Codex, and Cursor sessions.
session-recall
Shared semantic recall over local Claude Code, Codex, and Cursor history. Bundles MCP search tools, deep recall, guided setup, and a background freshness hook.