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/lint-and-fix)<a href="https://agentmods.dev/commands/hktitan/cursor-best-practices/lint-and-fix"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/lint-and-fix/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/lint-and-fix"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/lint-and-fix.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.00394 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
lint-and-fix 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 9d 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
Run the project's linter, auto-fix what can be fixed, and report remaining issues.
Steps
-
Run linter
- Use the project's actual commands (e.g.
npm run lint,eslint .,ruff check,cargo clippy,golangci-lint run). - If the project has multiple lint commands (e.g.
lint:js,lint:ts), run the relevant one(s) for the current changes.
- Use the project's actual commands (e.g.
-
Auto-fix issues
- Run the linter with auto-fix flag (e.g.
eslint --fix,ruff check --fix,cargo clippy --fix). - Apply fixes that can be automatically resolved.
- Re-run linter to verify fixes were applied.
- Run the linter with auto-fix flag (e.g.
-
Report remaining issues
- For each remaining issue that couldn't be auto-fixed, provide:
- Location (file, line, column)
- Rule/error code (e.g.
no-unused-vars,E501) - Description (what's wrong)
- Suggested fix (how to resolve manually)
- Categorize by severity:
- Error — Must fix (blocks build/CI)
- Warning — Should fix (code quality)
- Info — Nice to have (style suggestions)
- For each remaining issue that couldn't be auto-fixed, provide:
-
Summarize
- How many issues were auto-fixed
- How many issues remain (by severity)
- List of files that need manual attention
Rules
- Do not disable or ignore lint rules to make lint pass. Fix the code properly.
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant (e.g. linting style, rule preferences). - If the project doesn't have a linter configured, suggest setting one up rather than skipping.
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.
- 9d ago First seen · 35 lines · 0 tokens per session scan A 365edcff8158
lint-and-fix is a command published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 394 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
commit-msg
Cursor tooling: skills, rules, subagents.
handle-pr-comments
Fetch all PR comments, classify by severity, and present for user approval before acting.
self-review
Review only changed files in this branch Your primary goal is to provide valuable, trustworthy feedback while avoiding false positives and low-impact commentary.
create-pr
Commit changes and create a PR with proper formatting.
back-to-master-delete-branch
Cleanup current branch and switch to default branch with latest changes.
optimize-cursor-context
Analyze my Cursor base context and suggest optimizations.