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/sunmh207/entire-dashboardWrote 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/sunmh207/entire-dashboard/java-comments)<a href="https://agentmods.dev/rules/sunmh207/entire-dashboard/java-comments"><img src="https://agentmods.dev/badge/rules/sunmh207/entire-dashboard/java-comments/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/sunmh207/entire-dashboard/java-comments"><img src="https://agentmods.dev/badge/rules/sunmh207/entire-dashboard/java-comments.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.00264 |
| Opus 5.5 | $0.00000 | $0.00106 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
java-comments 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 Comment Style
Scope
All .java files.
Rules
-
Single-line comments must use
//. -
Documentation or multi-line comments must use
///. -
Do NOT use traditional Javadoc block comments (
/** ... */). -
Each line of a documentation comment must start with
///. -
Comments should preferably be written in English.
-
For long documentation comments that require formatting, use Markdown syntax. Do not use HTML tags inside comments.
Examples
Single-line comment
// Calculate total price int total = price * count;
Documentation comment
/// Returns the user by ID /// /// @param id user identifier /// @return user entity User getUser(Long id);
Documentation comment with Markdown
/// Returns repository information /// /// Features /// - Supports pagination /// - Supports filtering /// - Supports sorting /// /// @param query search query /// @return paginated result
Forbidden style
/**
- Returns the user by ID */ User getUser(Long id);
Forbidden formatting
/// Repository information /// /// Pagination /// Filtering ///
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 · 65 lines · 264 tokens per session scan A df303041988f
java-comments is a cursor rule published in the GitHub repository sunmh207/entire-dashboard (25 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 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
java-general-purpose-cursorrules-prompt-file
Cursor rules for Java General Purpose.
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
entity-class-conventions
A set of rules for Java classes that represent database records, called entities. It defines required annotations, automatic ID creation, lazy relationship loading, and field validation.
general-java-development-practices
A set of rules for writing Java code, including guidance on keeping designs focused, avoiding repetition, and following OWASP security practices. OWASP is a group that publishes guidance for building safer software.
java-spring
Optional Spring Boot example-pack coding rules. Apply only when editing an adopted project or spring-boot profile output.
secure-dev-java
These rules apply to all Java code in the repository (including Spring, Jakarta EE, and standalone apps) and aim to prevent common security risks through disciplined use of input validation, safe APIs, and secure coding patterns.