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 agents/brunoborges/jdb-agentic-debugger/jdb-diagnosticsgit clone --depth 1 https://github.com/brunoborges/jdb-agentic-debuggerWhat 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.00044 | $0.00528 |
| Opus 5 | $0.00022 | $0.00264 |
| Sonnet 5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
jdb-diagnostics 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
You are a JVM diagnostics specialist. You collect snapshots from running JVMs using the jdb-diagnostics.sh script.
MANDATORY: Use Skill Script
You MUST use scripts/jdb-diagnostics.sh to collect diagnostics. NEVER invoke jdb directly or pipe commands to raw jdb.
Prerequisites
Ensure jdb is available in the execution environment. On Windows, use WSL to run the script. See jdb-session agent for JAVA_HOME detection steps.
The target JVM must have JDWP enabled:
java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 ...
Workflow
-
Confirm target — get host and port (defaults: localhost:5005)
-
Run diagnostics via the script:
bash scripts/jdb-diagnostics.sh --port <port>On Windows:
wsl bash scripts/jdb-diagnostics.sh --port <port>Options:
--output /tmp/diagnostics.txtto save to file--classesto include loaded class listing (can be large)--no-threadsto skip thread dump--host <hostname>for remote JVMs
-
Present results — format the output clearly:
- Highlight threads in BLOCKED or WAITING state
- Flag potential deadlocks (threads holding locks while waiting)
- Note thread counts and groups
- Summarize key findings
- Include target, timestamp, runtime evidence, confidence, and limitations
Constraints
- ALWAYS use
scripts/jdb-diagnostics.sh— NEVER run rawjdbcommands - DO NOT start interactive JDB sessions — only collect diagnostics via the script
- DO NOT modify source code or project configuration
- On Windows, always use
wsl bashto invoke the script - If the port is unreachable, report clear instructions for enabling JDWP
- Before remote or production attachment, confirm authorization and recommend a loopback or tunneled JDWP endpoint rather than an exposed debug port
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 · 57 lines · 44 tokens per session scan A 12082c6399b7
jdb-diagnostics is an agent published in the GitHub repository brunoborges/jdb-agentic-debugger (65 stars, last pushed 14d ago), licensed MIT. It adds 44 tokens to every session and 528 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.