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/180-java-observability-loggingnpx skills add jabrena/cursor-rules-examples --skill 180-java-observability-logginggit 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.00085 | $0.00542 |
| Opus 5 | $0.00043 | $0.00271 |
| Sonnet 5 | $0.00017 | $0.00108 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
180-java-observability-logging 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 2d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Logging Best Practices
Implement effective Java logging following standardized frameworks, meaningful log levels, core practices (parameterized logging, exception handling, no sensitive data), flexible configuration, security-conscious logging, monitoring and alerting, and comprehensive logging validation through testing.
What is covered in this Skill?
- Standardized framework selection: SLF4J facade with Logback or Log4j2
- Meaningful and consistent log levels: ERROR, WARN, INFO, DEBUG, TRACE
- Core practices: parameterized logging, proper exception handling, avoiding sensitive data
- Configuration: environment-specific (logback.xml, log4j2.xml), output formats, log rotation
- Security: mask sensitive data, control log access, secure transmission, GDPR/HIPAA compliance
- Log monitoring and alerting: centralized aggregation (ELK, Splunk, Loki), automated alerts
- Logging validation through testing: assert log messages, verify formats, test levels, measure performance impact
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 logging 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 logging pattern
When to use this skill
- Review Java code for logging and observability
- Apply best practices for logging and observability in Java code
Reference
For detailed guidance, examples, and constraints, see references/180-java-observability-logging.md.
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.
- 2d ago First seen · 42 lines · 85 tokens per session scan A 6b6e7b2216be
180-java-observability-logging is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 85 tokens to every session and 542 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
azure-security-keyvault-keys-java
Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.
ponytail
Native Lean quality bar: no code → reuse → stdlib → platform → installed dep → one line → minimum. Split recovery, neighbor match, types, trust floors. Use when writing app code or when thin ponytail.mdc points here.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
redesign-existing-projects
Elaya audit for existing sites/apps that look generic, cheap, or AI-made. Diagnose first, then fix in place (fonts, color, states, layout, motion). Use when Mario says polish, audit, upgrade, or it looks horrible. Product apps apply diagnosis through premium-ui-craft values, not Elaya black/Geist/700ms. Upstream…
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.
tju-thesis-reviewer
严格按天津大学本科毕业设计（论文）规范审查和修订论文，覆盖前置页、版式、图表、公式、参考文献、数据口径和送审语气。Use when reviewing or revising Tianjin University undergraduate thesis tex/doc/docx/pdf files before submission or defense.