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/vepo/issuesWrote 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/rules/vepo/issues/issues-java)<a href="https://agentmods.dev/rules/vepo/issues/issues-java"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-java/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/rules/vepo/issues/issues-java"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-java.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.00298 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 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
Java conventions
Import order
java.*/javax.*/jakarta.*io.quarkus.*- Third-party
dev.vepo.issues.*
Style
- Formatting: issues-format-imports.mdc —
formatter.xml, no unused imports. - String building: issues-strings.mdc —
.formatted()first; no+concatenation in production code. - Type names: PascalCase classes, records, enums.
var
- Prefer
varwhen 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 prefixtb_;Longids.- Lazy associations by default; fetch in queries when needed for responses.
Exceptions
- Domain errors:
IssuesExceptionininfra. - Map to HTTP via
IssuesWebExceptionMapper/IssuesServerExceptionMapper.
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 · 42 lines · 0 tokens per session scan A 8752fd8e4556
issues-java is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo 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.
Other cursor rules, from other repositories
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
production-code
Production code rule — TDD precondition + Spring Boot 4 conventions.
graftcode-java
Mandatory Graftcode architecture rules for building Java backend services (plain Maven/Gradle modules exposed via Graftcode Gateway, not REST).
spring-boot-http-client
Spring Boot outbound HTTP contract for RestClient beans, timeouts, and repository-side remote calls.
java-springboot-standards
Java Spring Boot coding standards and patterns for your monorepo services.
spring-boot
Spring Boot: annotations, dependency injection, JPA patterns.