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/164-java-profiling-verifynpx skills add jabrena/cursor-rules-examples --skill 164-java-profiling-verifygit 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.00074 | $0.00499 |
| Opus 5 | $0.00037 | $0.00249 |
| Sonnet 5 | $0.00015 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
164-java-profiling-verify 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.
What it actually says
Java Profiling Workflow / Step 4 / Verify results
Verify performance optimizations through rigorous before/after comparison: ensure baseline and post-refactoring profiling data use identical test conditions, generate post-refactoring reports, compare metrics (memory, CPU, GC, threading), perform side-by-side flamegraph analysis, document findings in profiling-comparison-analysis-YYYYMMDD.md and profiling-final-results-YYYYMMDD.md, and validate success criteria.
What is covered in this Skill?
- Pre-refactoring baseline: run profiler with same load before changes
- Post-refactoring: generate new reports with identical test conditions
- Comparison: memory (leaks, allocations, GC), CPU (hotspots, contention), visual flamegraph comparison
- Documentation: profiler/docs/profiling-comparison-analysis-YYYYMMDD.md, profiler/docs/profiling-final-results-YYYYMMDD.md
- File naming: baseline/after suffixes, timestamp-based organization
- Validation: verify reports exist, compare metrics, identify regressions
Scope: Identical test conditions are critical. Document test scenarios. Validate application runs with refactored code before generating new reports.
Constraints
Use identical test conditions between baseline and post-refactoring. Verify both report sets are complete. Document test scenarios.
- CONSISTENCY: Use identical test conditions and load patterns for baseline and post-refactoring
- VALIDATE: Ensure both baseline and post-refactoring reports exist and are non-empty before comparison
- DOCUMENT: Record test scenarios and load patterns for reproduction
- BEFORE APPLYING: Read the reference for comparison templates and validation steps
When to use this skill
- Verify performance fix
- Performance benchmark
Reference
For detailed guidance, examples, and constraints, see references/164-java-profiling-verify.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 · 41 lines · 74 tokens per session scan A 129d10f4cc7f
164-java-profiling-verify is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 74 tokens to every session and 499 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.
java-dev
Java 开发规范，包含命名约定、异常处理、Spring Boot 最佳实践等.
cc-java-dev
Java 开发规范，包含命名约定、异常处理、Spring Boot 最佳实践等.
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…
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.
java-data-engineering-and-integration-services
Guides agents through Java-based data engineering services and processors. Use when building connectors, ingestion services, stream processors, metadata services, JVM batch tools, or operational integrations in Java.