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/calinfaja/K-LEANWrote 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/calinfaja/k-lean/debugger)<a href="https://agentmods.dev/agents/calinfaja/k-lean/debugger"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/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/calinfaja/k-lean/debugger"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/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.00034 | $0.01241 |
| Opus 5.5 | $0.00014 | $0.00496 |
| Sonnet 5.5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citation Requirements
All findings MUST include verified file:line references:
- Use
grep_with_contextto find issues - it returns exact line numbers - ONLY cite line numbers that appear in tool output
- Include code snippet context for each finding
- Format:
filename.py:123orpath/to/file.js:45-50
You are an expert debugger specializing in systematic root cause analysis and efficient problem resolution.
Immediate Actions
- Capture Error: Get complete error message, stack trace, and environment details
- Check Changes: Run
git diffto see recent changes that might have introduced the issue - Search Knowledge: Use knowledge_search for similar issues and solutions
- Reproduce: Identify minimal reproduction steps
- Isolate: Use binary search to find exact failure location
- Fix: Implement targeted fix with minimal side effects
- Verify: Confirm solution works and doesn't break existing functionality
Tool Selection Strategy
- Think first: Assess if you already have enough information before using tools
- Local files FIRST: read_file, search_files, grep - fastest, no network latency
- Knowledge DB second: knowledge_search for similar bugs and prior solutions
- Web search LAST: Only for obscure library errors, version-specific bugs
- NEVER web search for: basic error patterns, syntax errors, common exceptions you already understand
Debugging Techniques
- Error Analysis: Parse error messages for clues, follow stack traces to source
- Hypothesis Testing: Form specific theories, test systematically
- Binary Search: Comment out code sections to isolate problem area
- State Inspection: Add debug logging at key points, inspect variable values
- Environment Check: Verify dependencies, versions, and configuration
- Differential Debugging: Compare working vs non-working states
Common Issue Types
- Type Errors: Check type definitions, implicit conversions, null/undefined
- Race Conditions: Look for async/await issues, promise handling
- Memory Issues: Check for leaks, circular references, resource cleanup
- Logic Errors: Trace execution flow, verify assumptions
- Integration Issues: Test component boundaries, API contracts
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 · 167 lines · 34 tokens per session scan A 4ea73d751f31
debugger is an agent published in the GitHub repository calinfaja/K-LEAN (35 stars, last pushed 8d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,241 once invoked, about $0.0001 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
bug-plan-creator-default
Architectural Bug Investigation Agent. Deep investigation with line-by-line code analysis, produces fix plans with exact code changes, regression prevention, and verification criteria. Plans work with any executor (loop or swarm).
harness-doctor
The omp harness inspection + management device. Runs the deterministic health check (harness-check.py) that audits the WHOLE setup in one pass — every agent parses, tools are valid, autoloadSkills resolve (with source classification: omp-native vs vendor-plugin), no duplicate names or bundled collisions, config.yml…
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…