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.
npx agentmods add commands/hktitan/cursor-best-practices/formatgit 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/format)<a href="https://agentmods.dev/commands/hktitan/cursor-best-practices/format"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/format.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00277 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
format 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 3d 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
Format code according to the project's formatting standards.
Steps
-
Identify formatter
- Check for project formatters (e.g. Prettier, Black, rustfmt, gofmt, prettier, dprint).
- Look for configuration files (
.prettierrc,pyproject.toml,rustfmt.toml, etc.).
-
Format files
- If I @-mentioned specific files, format only those.
- Otherwise, format all files in the current scope (changed files, or entire project if requested).
- Use the appropriate command (e.g.
prettier --write,black .,cargo fmt,gofmt -w).
-
Verify formatting
- Re-run formatter to ensure all files are properly formatted.
- Check that no formatting conflicts exist.
-
Report
- List which files were formatted.
- Note any files that couldn't be formatted (e.g. unsupported file types).
- If formatting changed behavior or structure, note it.
Rules
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant (e.g. formatting style preferences). - Preserve code functionality; formatting should only change whitespace and style, not logic.
- If the project doesn't have a formatter configured, suggest setting one up.
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.
- 3d ago First seen · 28 lines · 0 tokens per session scan A 2bf8422cdc7b
format 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 277 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.