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-cursor-plugin/pinecone-assistantnpx skills add pinecone-io/pinecone-cursor-plugin --skill pinecone-assistantgit clone --depth 1 https://github.com/pinecone-io/pinecone-cursor-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.00071 | $0.00888 |
| Opus 5 | $0.00036 | $0.00444 |
| Sonnet 5 | $0.00014 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
pinecone-assistant 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.
This is a copy
89% identical to assistant — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pinecone Assistant
Pinecone Assistant is a fully managed RAG service. Upload documents, ask questions, get cited answers. No embedding pipelines or infrastructure required.
All scripts are in
scripts/relative to this skill directory. Run with:uv run scripts/script_name.py [arguments]
Whenever this skill asks the user to choose between options, confirm a destructive step, or pick from a list, ask in plain prose, list the options, and wait for their answer before continuing.
Operations
| What to do | Script | Key args |
|---|---|---|
| Create an assistant | scripts/create.py |
--name --instructions --region |
| Upload files | scripts/upload.py |
--assistant --source --patterns |
| Sync files (incremental) | scripts/sync.py |
--assistant --source --delete-missing --dry-run |
| Chat / ask a question | scripts/chat.py |
--assistant --message |
| Get context snippets | scripts/context.py |
--assistant --query --top-k |
| List assistants | scripts/list.py |
--files --json |
For full workflow details on any operation, read the relevant file in references/.
Natural Language Recognition
Proactively handle these patterns without requiring explicit commands:
Create: "create an assistant", "make an assistant called X", "set up an assistant for my docs" → See references/create.md
Upload: "upload my docs", "add files to my assistant", "index my documentation" → See references/upload.md
Sync: "sync my docs", "update my assistant", "keep assistant in sync", "refresh from ./docs" → See references/sync.md
Chat: "ask my assistant about X", "what does my assistant know about X", "chat with X" → See references/chat.md
Context: "search my assistant for X", "find context about X" → See references/context.md
List: "show my assistants", "what assistants do I have"
→ Run uv run scripts/list.py
What ships with it
18 files beside SKILL.md 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.
- references/chat.md 1.2 KB
- references/context.md 1.5 KB
- references/create.md 1.5 KB
- references/list.md 713 B
- references/sync.md 1.9 KB
- references/upload.md 1.7 KB
- scripts/__pycache__/chat.cpython-314.pyc 6.1 KB
- scripts/__pycache__/context.cpython-314.pyc 7.5 KB
- scripts/__pycache__/create.cpython-314.pyc 5.2 KB
- scripts/__pycache__/list.cpython-314.pyc 7.7 KB
- scripts/__pycache__/sync.cpython-314.pyc 16 KB
- scripts/__pycache__/upload.cpython-314.pyc 10 KB
- scripts/chat.py 4.9 KB runs code
- scripts/context.py 6.0 KB runs code
- scripts/create.py 3.9 KB runs code
- scripts/list.py 8.6 KB runs code
- scripts/sync.py 13 KB runs code
- scripts/upload.py 7.5 KB runs code
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 · 85 lines · 71 tokens per session scan A 1fd22db26e98
pinecone-assistant is a skill published in the GitHub repository pinecone-io/pinecone-cursor-plugin (1 stars, last pushed 19d ago), licensed MIT. It adds 71 tokens to every session and 888 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to assistant, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
assessing-vector-and-embedding-weaknesses
Test vector stores for embedding inversion, cross-tenant leakage, and poisoning.
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.
pinecone: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…
pinecone: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:mcp
Reference for the Pinecone MCP server tools. Documents all available tools - list-indexes, describe-index, describe-index-stats, create-index-for-model, upsert-records, search-records, cascading-search, and rerank-documents. Use when an agent needs to understand what Pinecone MCP tools are available, how to use them…
eval-engineer
Use when a user is unsure which Eval Engineer command to run for AI agents/RAG apps, needs onboarding/status for a .galileo workspace, or asks where to start.