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.
git clone --depth 1 https://github.com/HKTITAN/cursor-best-practicesWrote 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/hktitan/cursor-best-practices/fix-issue)<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/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/hktitan/cursor-best-practices/fix-issue"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/fix-issue.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.00210 |
| Opus 5.5 | $0.00000 | $0.00084 |
| Sonnet 5.5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
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 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
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
- Understand the reported bug or feature request (repro steps, expected vs actual, acceptance criteria).
- Locate the relevant code (search, @files, or project structure).
- Implement the fix or feature. Add or update tests as appropriate.
- Run the test suite and ensure nothing is broken. Fix any failures.
- 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/rulesorAGENTS.md.
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 · 17 lines · 0 tokens per session scan A 456532486ed4
fix-issue is a command published in the GitHub repository HKTITAN/cursor-best-practices (7 stars, last pushed 7mo 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.
Other commands, from other repositories
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
config-validate
Validate application configuration with schemas, per-environment rules, runtime checks, and secure handling of sensitive values.
smart-debug
AI-assisted smart debugging — parse error messages, stack traces, and failure patterns to identify root causes and produce a fix with automated observability steps.
team-debug
Debug issues using competing hypotheses with parallel investigation by multiple agents.
fix-issue
Fetch a GitHub issue, find the relevant code, implement the fix, verify, and open a PR.