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 commands/pinecone-io/pinecone-mcp/github-triagegit clone --depth 1 https://github.com/pinecone-io/pinecone-mcpWhat 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.00000 | $0.01704 |
| Opus 5 | $0.00000 | $0.00852 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00170 |
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 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.
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-issueinstead) - When you need to understand complex technical details before routing
Triage Process
-
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-infoif information has been provided)
- Type labels:
-
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
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 · 142 lines · 0 tokens per session scan A 6a764ee2a683
github-triage is a command published in the GitHub repository pinecone-io/pinecone-mcp (71 stars, last pushed 7d ago), 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).