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/create-bug.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/create-bug)<a href="https://agentmods.dev/commands/pinecone-io/pinecone-mcp/create-bug"><img src="https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/create-bug/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/create-bug"><img src="https://agentmods.dev/badge/commands/pinecone-io/pinecone-mcp/create-bug.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.00302 |
| Opus 5.5 | $0.00000 | $0.00121 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
create-bug 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.
What it actually says
create-bug
Create a Linear issue for this work in the "SDK Maintenance" project.
Give the issue these labels:
- tool:mcp
- Bug
Include the plan and any relevant context in the issue description.
If the plan was made to address a GitHub issue, be sure to include a link to the original GitHub issue in the description.
Every Linear issue created should include these additional instructions at the end of the description.
When the planned code changes are complete, the agent should take the following steps:
1. **Code Quality Review**
- Review JSDoc comments near the changed code to ensure they are still up to date
- Ensure the code compiles (TypeScript) and that unit tests pass
- Run the linter and formatter to verify no issues there
- npm run lint
- npm run format
- Ensure changes are adequately tested
2. **Create Pull Request**
- Create a PR
- Rename the PR with a title that follows the Conventional Commits 1.0.0 format
- Update the PR description with:
- A clear description of the problem and solution
- A reference to the related Github issue, if any, as well as the Linear issue number.
- Examples showing how to use the code that was changed
- A summary of the value and approach taken in the work (without overwhelming detail - reviewers can read the code for specifics)
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 · 36 lines · 0 tokens per session scan A 4b9d6afeea60
create-bug 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 302 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.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.