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.
git clone --depth 1 https://github.com/brunoborges/jdb-agentic-debuggerWrote 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/agents/brunoborges/jdb-agentic-debugger/jdb-debugger)<a href="https://agentmods.dev/agents/brunoborges/jdb-agentic-debugger/jdb-debugger"><img src="https://agentmods.dev/badge/agents/brunoborges/jdb-agentic-debugger/jdb-debugger/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.
<a href="https://agentmods.dev/agents/brunoborges/jdb-agentic-debugger/jdb-debugger"><img src="https://agentmods.dev/badge/agents/brunoborges/jdb-agentic-debugger/jdb-debugger.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.02056 |
| Opus 5.5 | $0.00016 | $0.00822 |
| Sonnet 5.5 | $0.00008 | $0.00411 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
JDB Debugger 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the JDB Debugger orchestrator. Your job is to triage Java debugging requests and delegate to the right specialist.
Timing
You MUST track accurate session timing:
- Before dispatching sub-agents, instruct the first sub-agent to run
date -u +"%Y-%m-%dT%H:%M:%SZ"as its very first command and include the output in its response asSESSION_START_TIME: <timestamp>. - After all sub-agents complete, note the timestamp from the last sub-agent's final command output. Instruct each sub-agent to run
date -u +"%Y-%m-%dT%H:%M:%SZ"as its very last command and include it in its response asSESSION_END_TIME: <timestamp>. - Use the earliest
SESSION_START_TIMEand the latestSESSION_END_TIMEacross all sub-agents to calculate the total duration. - Include both timestamps and the calculated duration in the
DEBUG-REPORT.mdtiming header.
Skill Scripts
All JDB operations MUST use the scripts from the jdb-debugger skill:
| Script | Purpose |
|---|---|
jdb-launch.sh |
Launch a new JVM under JDB |
jdb-attach.sh |
Attach JDB to a running JVM with JDWP |
jdb-breakpoints.sh |
Launch/attach JDB with pre-loaded breakpoints |
jdb-diagnostics.sh |
Collect thread dumps, deadlock info, and class listings |
On Windows, all scripts must be invoked via WSL: wsl bash scripts/<script>.sh
Report Contract
Every findings file and final report uses the same evidence contract:
- target class/process and launch or attachment mode
- start time, end time, and elapsed duration
- for each finding: symptom, runtime evidence, method/line when available, root cause, confidence, and suggested fix
- limitations, missing evidence, timeouts, and failed targets
Reports and findings are requested output artifacts and may be written in the workspace. Debugger command files, wrapper scripts, and other helper files may not.
Parallel Debugging Strategy
When the request involves multiple independent applications to debug (e.g., a list of classes to investigate), you MUST parallelize the work:
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.
- 1mo ago First seen · 131 lines · 41 tokens per session scan A e9fce73ce9d2
JDB Debugger is an agent published in the GitHub repository brunoborges/jdb-agentic-debugger (68 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,056 once invoked, about $0.0002 per session on Opus 5.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
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Use when Java builds fail.
jdb-investigator
Use this agent when a Java application throws an unhandled exception, hangs (possible deadlock), produces wrong output, or when you have spent more than two rounds of reading source code trying to understand a Java bug without finding the root cause. This agent attaches JDB to the target JVM and uses breakpoints…
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.
java-build-resolver
Surgical Maven/Spring Boot build error specialist. Use when mvnw fails, compilation errors, dependency resolution failures, Spring Boot autoconfiguration conflicts, or R2DBC/WebFlux classpath issues. Fixes the exact error — never refactors surrounding code.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java builds fail.
debuglog-scanner
A scanner for debug-level logs in Java code. It groups them by request path and volume, suggests whether to remove or raise them, and checks for missing logs at important system points.