jdwp-mcp: Command for Claude Code

.claude/commands/debug-performance.md

debug-performance is a command for Claude Code from dronsv/jdwp-mcp. It costs 0 tokens per session (115 once invoked), scanned A, original, from a forked repository, MIT.

A debugging command for Java applications that enables JDWP, Java's remote debugging protocol, and traces a slow request through the relevant code.

In plain words
What is it for?
It helps identify the slow method and check whether large collections, costly calculations, repeated database queries, or missing caches are responsible.
Why use it?
It provides a repeatable way to attach a debugger, find where time is spent, and investigate common causes of slow processing.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is dronsv/jdwp-mcp's own configuration. It tells Claude Code how to work on jdwp-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jdwp-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dronsv/jdwp-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dronsv/jdwp-mcp/main/.claude/commands/debug-performance.md
Clone the repo
git clone --depth 1 https://github.com/dronsv/jdwp-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for debug-performance

README.md
[![agentmods](https://agentmods.dev/badge/commands/dronsv/jdwp-mcp/debug-performance/github.svg)](https://agentmods.dev/commands/dronsv/jdwp-mcp/debug-performance)
Your own site
<a href="https://agentmods.dev/commands/dronsv/jdwp-mcp/debug-performance"><img src="https://agentmods.dev/badge/commands/dronsv/jdwp-mcp/debug-performance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for debug-performance

Your own site · 80×15
<a href="https://agentmods.dev/commands/dronsv/jdwp-mcp/debug-performance"><img src="https://agentmods.dev/badge/commands/dronsv/jdwp-mcp/debug-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin fork From a forked repository.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00115
Opus 5.5 $0.00000 $0.00046
Sonnet 5.5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00012

Measured 2mo ago against content hash eff09f0a8c16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

debug-performance 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 2mo 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.

.claude/commands/debug-performance.md · 11 lines

What it actually says

I'm debugging a Java app. Make sure it's running with JDWP enabled: java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 -jar app.jar

Attach to localhost:5005. A request is slow but doesn't hang. Trace the relevant processing package to see which methods are called and where time is spent. Identify the slow method, then inspect its state to find why it's slow — large collections, expensive computations, N+1 queries, or missing caches.

$ARGUMENTS

Changes

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.

  1. 2mo ago First seen · 11 lines · 0 tokens per session scan A eff09f0a8c16

Subscribe to this mod's changes

debug-performance is a command published in the GitHub repository dronsv/jdwp-mcp (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 115 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.