08-performance-resource

A set of Chinese-language rules for improving Java Virtual Machine performance and designing the data-access layer, the code that reads and writes databases.

In plain words
What is it for?
Use it when reviewing Java performance, collection choices, caching, connection pools, SQL field selection, joins, large tables, and database query patterns.
Why use it?
It helps avoid repeated object creation, memory leaks, inefficient queries, excessive joins, and common database access problems such as N+1 queries.

Cursor rule

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/movebrickschi/harness-engineering-mcp/08-performance-resource
Clone the repo
git clone --depth 1 https://github.com/movebrickschi/harness-engineering-mcp
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 420 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00420
Opus 5 $0.00000 $0.00210
Sonnet 5 $0.00000 $0.00084
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

08-performance-resource 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.

assets/rules/08-performance-resource.mdc · 46 lines

What it actually says

性能与资源管理

JVM优化

  • 对象池化:高创建成本对象(JSON Parser、Regex Pattern)使用static final常量或ThreadLocal缓存
  • 集合选型:频繁查询→HashMap,有序遍历→LinkedHashMap,并发读多→CopyOnWriteArrayList
  • Stream:大数据量避免长链式操作,CPU密集型任务可用parallel()
  • 内存泄漏:匿名内部类检查对外部类的隐式引用,监听器必须提供移除机制
// ✅ 正确:Pattern编译为静态常量
private static final Pattern EMAIL_PATTERN = Pattern.compile("^[\\w.-]+@[\\w.-]+$");

// ❌ 错误:每次调用都编译
public boolean validate(String email) {
    return Pattern.compile("^[\\w.-]+@[\\w.-]+$").matcher(email).matches();
}

数据访问层

规则 说明
禁止SELECT * 只查询需要的字段
JOIN不超过3表 超过则拆分为多次查询
千万级大表 必须考虑分库分表策略
N+1问题 自定义@Select JOIN查询或resultMap嵌套查询;生产环境开启SQL统计日志验证

缓存策略

场景 策略
读多写少 Read-Through Cache
写多读少 Write-Behind
缓存穿透 Bloom Filter

连接池

HikariCP的maximum-pool-size = (core_count × 2) + effective_spindle_count

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 · 46 lines · 420 tokens per session scan A 4f02a6b725a2

Subscribe to this mod's changes

08-performance-resource is a cursor rule published in the GitHub repository movebrickschi/harness-engineering-mcp (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 420 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.