issues-java

A set of Java coding rules for endpoint, repository, and database-entity code. It covers imports, formatting, naming, logging, exceptions, and common persistence settings.

In plain words
What is it for?
It helps organize imports, format strings, choose types and names, configure database entities, log safely, and map domain errors to HTTP responses.
Why use it?
It gives contributors consistent conventions for writing and reviewing Java code in the project.

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/vepo/issues/issues-java
Clone the repo
git clone --depth 1 https://github.com/vepo/issues

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 298 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.00298
Opus 5 $0.00000 $0.00149
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured yesterday against content hash 8752fd8e4556, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issues-java 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 yesterday.

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.

.cursor/rules/issues-java.mdc · 42 lines

What it actually says

Java conventions

Import order

  1. java.* / javax.* / jakarta.*
  2. io.quarkus.*
  3. Third-party
  4. dev.vepo.issues.*

Style

  • Formatting: issues-format-imports.mdcformatter.xml, no unused imports.
  • String building: issues-strings.mdc.formatted() first; no + concatenation in production code.
  • Type names: PascalCase classes, records, enums.

var

  • Prefer var when the RHS type is clear. Keep explicit types on fields and public API signatures.

Logging

  • SLF4J only — never System.out.
  • One static logger per class: LoggerFactory.getLogger(MyClass.class).
  • Parameterized messages; pass exception as last arg on error.
  • Do not log passwords or JWT tokens.

Entities

  • jakarta.persistence; table prefix tb_; Long ids.
  • Lazy associations by default; fetch in queries when needed for responses.

Exceptions

  • Domain errors: IssuesException in infra.
  • Map to HTTP via IssuesWebExceptionMapper / IssuesServerExceptionMapper.
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. yesterday First seen · 42 lines · 0 tokens per session scan A 8752fd8e4556

Subscribe to this mod's changes

issues-java is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 298 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.