cursorrules

A rule for writing Git commit messages in English using a specified type-and-scope format, such as a feature, bug fix, test, or documentation change.

In plain words
What is it for?
Useful whenever creating commits for features, fixes, documentation, refactoring, tests, styling, maintenance, or performance work.
Why use it?
It keeps commit history consistent and understandable for an English-speaking development team.

Cursor rule for Cursor

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 rules/huangpufan/hpf_linux_config/cursorrules
Clone the repo
git clone --depth 1 https://github.com/huangpufan/hpf_Linux_Config

Made for: Cursor.

Per session 91 This file is loaded in full into every session.
When invoked 91 The same file — it is already loaded in full.
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.00091 $0.00091
Opus 5 $0.00046 $0.00046
Sonnet 5 $0.00018 $0.00018
Haiku 4.5 $0.00009 $0.00009

Measured 2d ago against content hash b2fc85d7a4f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 2d 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.

.cursorrules · 15 lines

What it actually says

Commit Messages

The commit messages should be written in English only.

  • Format: [type](scope): description
  • Types:
    • feat: New feature
    • fix: Bug fix
    • docs: Documentation changes
    • style: Formatting, missing semicolons, etc.
    • refactor: Code refactoring
    • test: Adding tests
    • chore: Maintenance tasks
    • perf: optimize codes
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. 2d ago First seen · 15 lines · 91 tokens per session scan A b2fc85d7a4f2

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository huangpufan/hpf_Linux_Config (5 stars, last pushed 23d ago), licensed MIT. It adds 91 tokens to every session, about $0.0005 per session on Opus 5. 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.