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.
curl -O https://raw.githubusercontent.com/pinecone-io/pinecone-mcp/main/.cursor/commands/list-github-issues.mdgit clone --depth 1 https://github.com/pinecone-io/pinecone-mcpWrote 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.
[](https://agentmods.dev/commands/pinecone-io/pinecone-mcp/list-github-issues)<a href="https://agentmods.dev/commands/pinecone-io/pinecone-mcp/list-github-issues"><img src="https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/list-github-issues/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.
<a href="https://agentmods.dev/commands/pinecone-io/pinecone-mcp/list-github-issues"><img src="https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/list-github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00481 |
| Opus 5.5 | $0.00000 | $0.00192 |
| Sonnet 5.5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
list-github-issues 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
list-github-issues
List GitHub issues for batch triage or review. This helper command fetches issues and prepares them for processing with github-triage.
Usage
This command helps you get a list of GitHub issues to process. You can then use the issue URLs/numbers with github-triage for iterative processing.
Output Format
The command should provide:
- Issue numbers and URLs
- Current labels (especially status labels)
- Last updated date
- Issue title
- Priority suggestion based on labels and recency
Filtering Options
When listing issues, consider filtering by:
- State:
open,closed - Labels:
status:needs-triage,needs-info,needs-reproduction,needs-investigation - Sort order:
created,updated,comments - Limit: Number of issues to fetch (start with 20-50 for manageable batches)
Suggested Workflow
-
List untriaged issues:
List open issues with no status labels or with "status:needs-triage" label -
Prioritize the list:
- Issues without any status labels (highest priority)
- Issues with
needs-infothat have new comments - Issues with
needs-reproductionthat have new information - Recently updated issues
-
Process iteratively:
- Take the first N issues from the prioritized list
- For each issue, run
github-triagewith the issue URL/number - Review results before proceeding to the next batch
-
Track progress:
- Note which issues were processed
- Identify issues that need follow-up (investigation, waiting for info, etc.)
- Update your list to exclude already-processed issues
Integration with github-triage
After listing issues, use the issue URLs/numbers with github-triage:
- Provide issue URLs:
https://github.com/owner/repo/issues/123 - Or provide issue numbers with repository context
- Process one at a time or in small batches
The github-triage command is idempotent, so you can safely re-run it on issues that have already been processed.
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.
- 1mo ago First seen · 58 lines · 0 tokens per session scan A 73b26031f6df
list-github-issues 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 481 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
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.