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.
npx agentmods add skills/pinecone-io/pinecone-claude-code-plugin/querynpx skills add pinecone-io/pinecone-claude-code-plugin --skill querygit clone --depth 1 https://github.com/pinecone-io/pinecone-claude-code-pluginWhat 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 | $0.00074 | $0.01139 |
| Opus 5 | $0.00037 | $0.00570 |
| Sonnet 5 | $0.00015 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
pinecone:query 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- pinecone-query — 92% identical, 22 lines differ
- pinecone-query — 91% identical, 19 lines differ
- query — 86% identical, 21 lines differ
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pinecone Query Skill
Search for records in Pinecone integrated indexes using natural language text queries via the Pinecone MCP server.
Whenever this skill asks the user to choose between options, confirm a destructive step, or pick from a list, use the AskUserQuestion tool rather than plain prose. Fall back to prose only if the tool is unavailable.
What is this skill for?
This skill provides a simple way to query integrated indexes (indexes with built-in Pinecone embedding models) using text queries. The MCP server automatically converts your text into embeddings and searches the index.
Prerequisites
Required:
- ✅ Pinecone MCP server must be configured - Check if MCP tools are available
- ✅ PINECONE_API_KEY environment variable must be set - Get a free API key at https://app.pinecone.io/?sessionType=signup
- ✅ Index must be an integrated index - Uses Pinecone embedding models (e.g., multilingual-e5-large, llama-text-embed-v2, pinecone-sparse-english-v0)
When NOT to use this skill
Use the pinecone:cli skill instead if:
- ❌ Your index is a standard index (no integrated embedding model)
- ❌ You need to query with custom vector values (not text)
- ❌ You need advanced vector operations (fetch by ID, list vectors, bulk operations)
- ❌ Your index uses third-party embedding models (OpenAI, HuggingFace, Cohere)
MCP Limitation: The Pinecone MCP currently only supports integrated indexes. For all other use cases, use the pinecone:cli skill.
How it works
Utilize Pinecone MCP's search-records tool to search for records within a specified Pinecone integrated index using a text query.
Workflow
IMPORTANT: Before proceeding, verify the Pinecone MCP tools are available. If MCP tools are not accessible:
- Inform the user that the Pinecone MCP server needs to be configured
- Check if
PINECONE_API_KEYenvironment variable is set - Direct them to the MCP setup documentation or the
pinecone:helpskill
- Parse the user's input for:
query(required): The text to search for.index(required): The name of the Pinecone index to search.namespace(optional): The namespace within the index.reranker(optional): The reranking model to use for improved relevance.
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 · 89 lines · 74 tokens per session scan A 1a24f97102b5
pinecone:query is a skill published in the GitHub repository pinecone-io/pinecone-claude-code-plugin (68 stars, last pushed 18d ago), licensed MIT. It adds 74 tokens to every session and 1,139 once invoked, about $0.0004 per session on Opus 5. 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 skills, from other repositories
help
Overview of all available Pinecone skills and what a user needs to get started. Invoke when a user asks what skills are available, how to get started with Pinecone, or what they need to set up before using any Pinecone skill.
assistant
Create, manage, and chat with Pinecone Assistants for document Q&A with citations. Handles all assistant operations - create, upload, sync, chat, context retrieval, and list. Recognizes natural language like "create an assistant from my docs", "ask my assistant about X", or "upload my docs to Pinecone".
pinecone-help
Overview of all available Pinecone skills and what a user needs to get started. Invoke when a user asks what skills are available, how to get started with Pinecone, or what they need to set up before using any Pinecone skill.
quickstart
Interactive Pinecone quickstart for new developers. Choose between two paths - Database (create an integrated index, upsert data, and query using Pinecone MCP + Python) or Assistant (create a Pinecone Assistant for document Q&A). Use when a user wants to get started with Pinecone for the first time or wants a guided…
cli
Guide for using the Pinecone CLI (pc) to manage Pinecone resources from the terminal. The CLI supports ALL index types (standard, integrated, sparse) and all vector operations — unlike the MCP which only supports integrated indexes. Use for batch operations, vector management, backups, namespaces, CI/CD automation…
pinecone-n8n
Build n8n workflows using the Pinecone Assistant node or Pinecone Vector Store node. Use when building RAG pipelines, chat-with-docs workflows, configuring Pinecone nodes in n8n, troubleshooting Pinecone n8n nodes, or asking about best practices for Pinecone in n8n.