fix-issue

fix-issue is a command for coding agents from HKTITAN/cursor-best-practices. It costs 0 tokens per session (210 once invoked), scanned A, original, MIT.

A command for investigating and fixing a reported software issue or feature request. It can use an issue number, URL, or description as the starting point.

In plain words
What is it for?
Use it to locate relevant code, implement a fix or feature, update tests, run the test suite, and explain how to verify the result.
Why use it?
It organizes the work from understanding the report through code changes and testing, so verification is not skipped.

Command

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/hktitan/cursor-best-practices/fix-issue
Clone the repo
git clone --depth 1 https://github.com/HKTITAN/cursor-best-practices

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/fix-issue.svg)](https://agentmods.dev/commands/hktitan/cursor-best-practices/fix-issue)
Your own site
<a href="https://agentmods.dev/commands/hktitan/cursor-best-practices/fix-issue"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/fix-issue.svg" alt="Measured on agentmods" 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 210 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.00210
Opus 5 $0.00000 $0.00105
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

Measured 4d ago against content hash 456532486ed4, 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 4d 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-best-practices/assets/templates/commands/fix-issue.md · 17 lines

What it actually says

Fix the issue described below.

Context: If I provided an issue number or URL after the command (e.g. /fix-issue 123 or /fix-issue https://github.com/org/repo/issues/456), use that to fetch or reference the issue. Otherwise, use the rest of my message as the issue description.

Steps

  1. Understand the reported bug or feature request (repro steps, expected vs actual, acceptance criteria).
  2. Locate the relevant code (search, @files, or project structure).
  3. Implement the fix or feature. Add or update tests as appropriate.
  4. Run the test suite and ensure nothing is broken. Fix any failures.
  5. Summarize what you changed and how to verify it (e.g. run X, check Y).

Rules

  • Do not skip tests. Run them and fix failures before considering the task done.
  • Apply project rules from .cursor/rules or AGENTS.md.
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. 4d ago First seen · 17 lines · 0 tokens per session scan A 456532486ed4

Subscribe to this mod's changes

fix-issue is a command published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 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.