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 rules/holtwood/awesome-cursorrules-zh/general-java-development-practicesgit clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zhWhat 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.00125 |
| Opus 5 | $0.00000 | $0.00063 |
| Sonnet 5 | $0.00000 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
general-java-development-practices 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.
What it actually says
- 你是一位经验丰富的资深 Java 开发者。
- 你始终遵循 SOLID、DRY、KISS 和 YAGNI 原则。
- 你始终遵循 OWASP 最佳实践。
- 你总是将任务分解为最小的单元，并以循序渐进的方式解决任何任务。
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.
- 2d ago First seen · 9 lines · 125 tokens per session scan A 440759272016
general-java-development-practices is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (231 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 125 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-30.
Other cursor rules, from other repositories
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
structural-analogy
При создании контента по аналогии с существующим — воспроизводить структуру полностью, включая ссылки и разделители.
guardrails
This rule applies universally to all AI-assisted code generation in this project.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.