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 skills/jabrena/cursor-rules-examples/144-java-data-oriented-programmingnpx skills add jabrena/cursor-rules-examples --skill 144-java-data-oriented-programminggit clone --depth 1 https://github.com/jabrena/cursor-rules-examplesWhat 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.00088 | $0.00548 |
| Opus 5 | $0.00044 | $0.00274 |
| Sonnet 5 | $0.00018 | $0.00110 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade A, and why
144-java-data-oriented-programming 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Data-Oriented Programming Best Practices
Apply data-oriented programming in Java: separate data from behavior with records, use immutable data structures, pure functions for transformations, flat denormalized structures with ID references, generic-to-specific type conversion when needed, pure validation functions, and flexible generic data access layers. All transformations should be explicit, traceable, and composed of clear pure functional steps.
What is covered in this Skill?
- Separation of concerns: data structures (records, POJOs) vs behavior (utility classes, services)
- Immutability: records, final fields, transformations produce new instances
- Pure data transformations: functions depending only on inputs, no side effects
- Flat and denormalized data: ID references instead of deep nesting
- Generic until specific: Map<String,Object> for dynamic data, convert to records when processing
- Data integrity: pure validation functions returning validation results
- Flexible generic data access: generic CRUD interfaces, interchangeable implementations
Scope: The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.
Constraints
Before applying any data-oriented programming recommendations, ensure the project compiles. Compilation failure is a blocking condition. After applying improvements, run full verification.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately — do not proceed until resolved
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each data-oriented programming pattern
When to use this skill
- Review Java code for data-oriented programming
- Apply best practices for data-oriented programming in Java code
Reference
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 88 tokens per session scan A e3308743f1ab
144-java-data-oriented-programming is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 88 tokens to every session and 548 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
complexity
Wire and satisfy cyclomatic complexity lint. Detect the repo's existing linter, set or keep a cap (default 10), extract until green, never disable the rule. Use when complexity.mdc globs match, lint reports C901/complexity, or the user asks for simpler / less nested code.
uikit-expert
Write, review, or improve UIKit code following best practices for view controller lifecycle, Auto Layout, collection views, navigation, animation, memory management, and modern iOS 18–26 APIs. Use when building new UIKit features, refactoring existing views or view controllers, reviewing code quality, adopting modern…
debugging
Debugs difficult, intermittent, cross-layer, or regression bugs evidence before fixes. Use when the cause is unknown, normal debugging stalled, or the user asks to hunt, diagnose, or root-cause a bug.
testing
Test writing workflows: TDD order, mocks, house gauntlet, regression naming. Use when writing/editing tests or when testing.mdc globs match. Thin rule = roofs; this skill = procedure.
design-stack
Router for Mario's Design agent. Picks one UI skill plus premium-ui-craft. Use at the start of any Product Designer / @Design / UX/UI turn.
now
Write or resume NOW.md (session state). Use when continuing tomorrow, switching chats/models, pausing a feature, or the user mentions NOW.md, session continuity, or the old name handoff.