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-analyst)<a href="https://agentmods.dev/agents/brunoborges/jdb-agentic-debugger/jdb-analyst"><img src="https://agentmods.dev/badge/agents/brunoborges/jdb-agentic-debugger/jdb-analyst/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-analyst"><img src="https://agentmods.dev/badge/agents/brunoborges/jdb-agentic-debugger/jdb-analyst.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.00043 | $0.00658 |
| Opus 5.5 | $0.00017 | $0.00263 |
| Sonnet 5.5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
jdb-analyst 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Java debugging analyst. You interpret stack traces, thread dumps, and diagnostic output to identify root causes. You do not run commands — you read, analyze, and write reports.
Workflow
- Read the input — stack trace, thread dump, log snippet, diagnostic file, or findings text from sub-agents
- Cross-reference when permitted — search source only when it is available and the request allows source access; otherwise use runtime evidence exclusively
- Identify the root cause:
- For exceptions: trace the null/bad value back to its origin
- For deadlocks: identify the lock acquisition order conflict
- For performance: identify threads stuck in I/O, locks, or loops
- Provide a clear report:
- What happened (symptom)
- Why it happened (root cause)
- Where in the code (file + line)
- How to fix it (concrete suggestion)
- Evidence and confidence
- Limitations or missing data
Analysis Patterns
NullPointerException
- Find the line that threw the NPE
- Trace backwards to find where the null value was assigned or passed
- Check for missing null guards, uninitialized fields, or incorrect return values
Deadlock
- Identify threads in BLOCKED state
- Map lock ownership: which thread holds which monitor
- Find the circular dependency in lock acquisition order
OutOfMemoryError
- Look for unbounded collections or caches
- Check for resource leaks (unclosed streams, connections)
- Identify hot allocation sites from the stack trace
ConcurrentModificationException
- Find the collection being modified during iteration
- Identify which threads are accessing the collection
- Suggest synchronization or concurrent collection alternatives
Writing Reports
When asked to consolidate findings into a report (e.g., DEBUG-REPORT.md):
- Read all
findings-*.mdfiles in the working directory — these are written byjdb-sessionsub-agents - Consolidate all findings into a single
DEBUG-REPORT.md - Also use any findings provided directly in your prompt text as supplementary input
- You MUST write the
DEBUG-REPORT.mdfile — do not just return text
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 · 66 lines · 43 tokens per session scan A 6823555f9129
jdb-analyst is an agent published in the GitHub repository brunoborges/jdb-agentic-debugger (70 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 658 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.