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/alkoleft/platform-context-exporterWrote 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/alkoleft/platform-context-exporter/113-java-general-guidelines)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/113-java-general-guidelines"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/113-java-general-guidelines/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/alkoleft/platform-context-exporter/113-java-general-guidelines"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/113-java-general-guidelines.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.05375 | $0.05375 |
| Opus 5.5 | $0.02150 | $0.02150 |
| Sonnet 5.5 | $0.01075 | $0.01075 |
| Haiku 4.5 | $0.00537 | $0.00537 |
Grade A, and why
113-java-general-guidelines 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.
How it starts
The opening of the file, as written. The whole thing — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java General Guidelines
This document outlines general Java coding guidelines covering fundamental aspects such as naming conventions for packages, classes, methods, variables, and constants; code formatting rules including indentation, line length, brace style, and whitespace usage; standards for organizing import statements; best practices for Javadoc documentation; and comprehensive error and exception handling with a strong focus on security, including avoiding sensitive information exposure, catching specific exceptions, and secure resource management.
Implementing These Principles
These guidelines are built upon the following core principles:
- Clarity and Consistency in Naming: Adhere to standard Java naming conventions for all code elements (packages, classes, methods, variables, constants). This promotes code that is intuitive, predictable, and easier for developers to understand and navigate.
- Readability through Formatting: Consistently apply formatting rules for indentation, line length, brace style, and whitespace. Well-formatted code is significantly easier to read, debug, and maintain.
- Organized Import Statements: Structure import statements logically by grouping related packages and alphabetizing within those groups. Avoid wildcard imports to ensure clarity about class origins and prevent namespace conflicts.
- Effective Documentation: Strive for self-documenting code. For public APIs, complex algorithms, non-obvious business logic, or any part of the code that isn't immediately clear, provide comprehensive Javadoc. Good documentation aids understanding, usage, and maintenance.
- Robust and Secure Error Handling: Implement thorough error and exception handling with a strong focus on security. This includes using specific exceptions, managing resources diligently (preferably with try-with-resources), preventing the leakage of sensitive information in logs or error messages, and never "swallowing" exceptions without proper handling or justification. Resilient and secure applications depend on robust error management.
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 · 545 lines · 5,375 tokens per session scan A a26c1b8a714f
113-java-general-guidelines is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It adds 5,375 tokens to every session, about $0.0215 per session on Opus 5.5. 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
1c-extension-patterns
A set of rules and examples for extending 1C configurations with BSL code and XML role metadata. 1C is an enterprise business-application platform, and BSL is its programming language.
testing-patterns
A set of rules and examples for testing 1C code with YaXUnit and Vanessa Automation. YaXUnit is used for unit tests of individual functions, while Vanessa Automation describes user scenarios as “given, when, then” steps.
integrations
A development rule for building 1C integrations with external systems through HTTP APIs. It recommends first making and testing the requests in Python, then translating the working version into 1C’s BSL language.
kotlin
You are a Senior Kotlin programmer with experience in the Android framework and a preference for clean programming and design patterns.
1c-coding-standards
Coding standards for BSL, the programming language used by the 1C business software platform. They cover naming, method documentation, database queries, collections, client-server code, and performance practices.
1c-skd-two-pass-preprocessing
A two-pass method for changing 1C report output before detailed records are combined into grouped totals. 1C's report system, СКД, builds reports by grouping and summarizing data.