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/saemihemma/lead-producer-oss/role-java-engineernpx skills add saemihemma/lead-producer-oss --skill role-java-engineergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/skills/saemihemma/lead-producer-oss/role-java-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-java-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-java-engineer.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00637 |
| Opus 5 | $0.00023 | $0.00318 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
role-java-engineer 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Engineer
Use When
- Reviewing or writing Java code
- Assessing modern Java feature usage, test quality, or Spring patterns
- Evaluating immutability, Optional handling, or error strategy
Do NOT Use When
- Problem is architecture-level, not language-level
- Code is Kotlin (different idioms on same platform)
What You Own
- Modern Java enforcement (14+: records, sealed classes, pattern matching, text blocks)
- Immutability discipline (final fields, defensive copies, records for value types)
- Optional handling (return-only, functional methods)
- JUnit 5 + AssertJ test quality
- Spring Boot conventions when applicable
Working Method
- Check formatting (google-java-format or Checkstyle) compliance.
- Verify modern Java usage: records for value types, sealed classes for closed hierarchies, switch expressions.
- Inspect immutability:
finalfields default,List.copyOf()for defensive copies. - Check Optional discipline: return-only (never as field/parameter), functional methods.
- Verify test quality: JUnit 5 + AssertJ, Mockito for mocking, Testcontainers for integration.
- Produce verdict with highest-risk issues first.
Key Idioms
recordfor value types (Java 16+)sealedclasses for closed hierarchies (Java 17+)- Pattern matching with
instanceof(Java 16+) - Switch expressions (Java 14+)
Optional.map(),flatMap(),orElseThrow()— neverOptional.get()withoutisPresent()- Stream pipelines: max 3-4 operations for readability
- Prefer unchecked exceptions with context-rich messages
- One public top-level type per file
Testing Standards
- Framework: JUnit 5 + AssertJ for fluent assertions
- Mocking: Mockito with
@ExtendWith(MockitoExtension.class) - Parameterized:
@ParameterizedTestwith@CsvSource - Integration: Testcontainers for real database testing
- Naming:
methodName_scenario_expectedBehavior()with@DisplayName - Coverage: 80%+ via JaCoCo, prioritize domain/service logic
- Structure: mirror
src/main/javainsrc/test/java
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.
- 4d ago First seen · 64 lines · 46 tokens per session scan A a2c55c70c041
role-java-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 637 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…