fix-issue

A command that works through a GitHub issue from investigation to pull request. GitHub issues are tracked requests for bug fixes, changes, or other work in a code repository.

In plain words
What is it for?
Use it to inspect an issue, find related code, implement and test a fix, run Rust checks, create a commit, and open a pull request.
Why use it?
It organizes the routine work of understanding an issue, changing the code, testing it, and submitting the result for review.

Command for Cursor

Install

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.

agentmods
npx agentmods add commands/platinoff/poolai/fix-issue
Clone the repo
git clone --depth 1 https://github.com/platinoff/poolAI

Made for: Cursor.

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 96 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00096
Opus 5 $0.00000 $0.00048
Sonnet 5 $0.00000 $0.00019
Haiku 4.5 $0.00000 $0.00010

Measured yesterday against content hash 2626a3eaa52d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-issue 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 yesterday.

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/fix-issue.md · 14 lines

What it actually says

Fix Issue Command

Fix a GitHub issue.

  1. Fetch issue details using gh issue view <number>
  2. Find relevant code using codebase search
  3. Implement the fix following project patterns
  4. Add tests for the fix
  5. Run cargo fmt, cargo clippy, cargo test
  6. Create a commit with Conventional Commits format
  7. Open a pull request with gh pr create

Return PR URL when done.

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. yesterday First seen · 14 lines · 0 tokens per session scan A 2626a3eaa52d

Subscribe to this mod's changes

fix-issue is a command published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 96 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-31.