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.
npx agentmods add rules/alkoleft/platform-context-exporter/112-java-type-designgit clone --depth 1 https://github.com/alkoleft/platform-context-exporterWhat 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 | $0.00000 | $0.04583 |
| Opus 5 | $0.00000 | $0.02292 |
| Sonnet 5 | $0.00000 | $0.00917 |
| Haiku 4.5 | $0.00000 | $0.00458 |
Grade A, and why
112-java-type-design 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.
How it starts
The opening of the file, as written. The whole thing — 612 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Type Design Thinking in Java
Type design thinking in Java applies typography principles to code structure and organization. Just as typography creates readable, accessible text, thoughtful type design in Java produces maintainable, comprehensible code.
Implementing These Principles
- Start with domain modeling: Sketch your type system before coding.
- Create a type style guide: Document naming conventions and patterns.
- Review for type consistency: Periodically check for style adherence.
- Refactor toward clearer type expressions: Improve existing code.
- Use tools to enforce style: Configure linters and static analyzers.
Remember, good type design in Java is about communication - making your code's intent clear both to the compiler and to other developers.
Table of contents
- Rule 1: Establish a Clear Type Hierarchy
- Rule 2: Use Consistent Naming Conventions (Your Type's "Font Family")
- Rule 3: Embrace Whitespace (Kerning and Leading)
- Rule 4: Create Type-Safe Wrappers (Type as Communication)
- Rule 5: Leverage Generic Type Parameters (Responsive Typography)
- Rule 6: Create Domain-Specific Languages (Typography with Character)
- Rule 7: Use Consistent Type "Weights" (Bold, Regular, Light)
- Rule 8: Apply Type Contrast Through Interfaces
- Rule 9: Create Type Alignment Through Method Signatures
- Rule 10: Design for Clear Type Readability and Comprehension
- Rule 11: Use BigDecimal for Precision-Sensitive Calculations
- Rule 12: Strategic Type Selection for Methods and Algorithms
Rule 1: Establish a Clear Type Hierarchy
Title: Establish a Clear Type Hierarchy Description: This rule focuses on organizing classes and interfaces into a logical structure using inheritance and composition. A clear hierarchy makes the relationships between types explicit, improving code navigation and understanding. It often involves using nested static classes for closely related types.
Good example:
// GOOD: Clear type hierarchy with descriptive names
public class OrderManagement {
public static class Order {
private List<OrderItem> items;
private Customer customer;
// ...
}
public static class OrderItem {
private Product product;
private int quantity;
// ...
}
}
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.
- yesterday First seen · 612 lines · 0 tokens per session scan A 9c2f78fbcb1b
112-java-type-design is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,583 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
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
anti_patterns
Критические антипаттерны 1С: запрос в цикле, реквизиты через точку.
bsl-ssl
Переиспользование БСП, разметка правок типовых модулей, устаревшие объекты.
edt-form-xml-requirements
Требования EDT к XML-формам (Form.form): extInfo, дефолты полей.
sdd-workflow
Specification-Driven Development: 9-фазный workflow разработки.
1c-report-direct-query
Прямой запрос в отчётах 1С (СКД) без схемы компоновки.