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/pr)<a href="https://agentmods.dev/commands/hktitan/cursor-best-practices/pr"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/pr/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/pr"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/pr.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.00289 |
| Opus 5.5 | $0.00000 | $0.00116 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
pr 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
Help me create a pull request for the current branch.
Steps
-
Summarize changes
- Use
git diff,git log, or recent commits to understand what changed. - If I've @-mentioned files or provided context, use that too.
- Briefly list: what was added, changed, or removed, and why.
- Use
-
Propose PR title and description
- Title: Short, imperative (e.g. "Add email validation to login" or "Fix null deref in user loader").
- Description: Include:
- What changed (high level).
- Why (bug fix, feature, refactor).
- How to test (steps or commands).
- Any breaking changes or migration notes if relevant.
-
Suggest a review checklist
- e.g. [ ] Tests run and pass
- Lint passes
- Migrations applied (if any)
- Docs updated (if relevant)
- No secrets or debug code committed
Adapt to the project (e.g. "run make test", "apply .cursor/rules").
Apply project rules
Follow any project rules in .cursor/rules or AGENTS.md (e.g. PR format, scope, conventions).
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 · 30 lines · 0 tokens per session scan A 3db647fe409d
pr 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 289 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.
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.
clean
Repository hygiene — clean temp files, organize execution folders.
commit
Git commit with conventional commits format.
revert
Git-aware undo by logical work unit (track, phase, or task).