pinecone-mcp: Command for Claude Code

.cursor/commands/github-triage.md

github-triage is a command for Claude Code, Cursor from pinecone-io/pinecone-mcp. It costs 0 tokens per session (1,704 once invoked), scanned A, original, Apache-2.0.

Ein Befehl zur schnellen ersten Einordnung und Weiterleitung von GitHub-Issues, also gemeldeten Fehlern, Fragen oder Änderungswünschen. Er bewertet die Art und grobe Priorität eines Issues und prüft den bisherigen Status.

In plain words
What is it for?
Für die erste Bearbeitung neuer oder aktualisierter GitHub-Issues. Er hilft bei der Einordnung als Fehler, Funktionswunsch, Frage oder Dokumentationsproblem sowie beim Anfordern fehlender Informationen und beim Umgang mit veralteten Meldungen.
Why use it?
Er verhindert doppelte Vorgänge und unnötige Kommentare, indem er vorhandene Issues, Linear-Einträge und Labels zuerst berücksichtigt. So kann eine neue Meldung schnell dem passenden weiteren Ablauf zugeordnet werden.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is pinecone-io/pinecone-mcp's own configuration. It tells Claude Code and Cursor how to work on pinecone-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pinecone-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pinecone-io/pinecone-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pinecone-io/pinecone-mcp/main/.cursor/commands/github-triage.md
Clone the repo
git clone --depth 1 https://github.com/pinecone-io/pinecone-mcp

Made for: Claude Code, Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for github-triage

README.md
[![agentmods](https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/github-triage/github.svg)](https://agentmods.dev/commands/pinecone-io/pinecone-mcp/github-triage)
Your own site
<a href="https://agentmods.dev/commands/pinecone-io/pinecone-mcp/github-triage"><img src="https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/github-triage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for github-triage

Your own site · 80×15
<a href="https://agentmods.dev/commands/pinecone-io/pinecone-mcp/github-triage"><img src="https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/github-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01704
Opus 5.5 $0.00000 $0.00682
Sonnet 5.5 $0.00000 $0.00341
Haiku 4.5 $0.00000 $0.00170

Measured 1mo ago against content hash 6a764ee2a683, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-triage 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 1mo 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.

.cursor/commands/github-triage.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

github-triage

Quick triage and routing of GitHub issues. This is the first step for handling new or updated GitHub issues.

IMPORTANT: This command must be idempotent. Before taking any action, check the current state to avoid duplicates:

  • Check if a Linear issue already exists for this GitHub issue (search by GitHub issue URL or number)
  • Check if comments requesting information have already been posted
  • Check if the issue has already been closed
  • Check existing labels before adding or removing any

When to use this command:

  • Initial triage of new GitHub issues
  • Quick assessment and routing
  • Requesting missing information
  • Managing issue lifecycle (labels, closing stale issues)

When NOT to use this command:

  • For deep code analysis or root cause investigation (use investigate-github-issue instead)
  • When you need to understand complex technical details before routing

Triage Process

  1. Categorize the issue

    • Determine if it's a bug, feature request, question, documentation issue, or other
    • Assess priority based on severity, impact, and user needs (surface-level assessment)
    • Check if it's a duplicate of existing issues (GitHub or Linear)
    • Update labels: Ensure appropriate labels are applied:
      • Type labels: bug, enhancement, question, documentation, etc.
      • Status labels: needs-info, needs-reproduction, needs-investigation, in-progress, etc.
      • Priority labels: priority:high, priority:medium, priority:low, etc.
      • Component/area labels if applicable
      • Check first: Review existing labels before adding new ones
      • Only add: Labels that are missing and appropriate
      • Remove: Incorrect or outdated labels (e.g., remove needs-info if information has been provided)
  2. Extract key information

    • Summarize the problem or request clearly
    • Identify affected components or areas of the codebase (high-level)
    • Note any relevant context (OS, Node.js version, TypeScript version, SDK version, etc.)
    • Extract any code examples or error messages

Read the full file on GitHub · 142 lines

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.

  1. 1mo ago First seen · 142 lines · 0 tokens per session scan A 6a764ee2a683

Subscribe to this mod's changes

github-triage is a command published in the GitHub repository pinecone-io/pinecone-mcp (72 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,704 tokens. 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.