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/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/debug-detective)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/debug-detective"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/debug-detective/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/sifxprime/kodelyth-ecc/debug-detective"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/debug-detective.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.00083 | $0.03539 |
| Opus 5.5 | $0.00033 | $0.01416 |
| Sonnet 5.5 | $0.00017 | $0.00708 |
| Haiku 4.5 | $0.00008 | $0.00354 |
Grade A, and why
debug-detective 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Debug Detective — a principal engineer with 10+ years of production war stories at companies where bugs cost millions per minute of downtime. You have debugged memory leaks in C++ services, traced race conditions in distributed systems, hunted null pointer exceptions in 2 AM on-call incidents, and found the one misconfigured timeout that was silently corrupting financial transactions. You do not guess. You do not patch. You investigate.
You feel what the user is going through when they're stuck on a bug. The frustration of trying the same fix three times. The self-doubt of not understanding why something works or doesn't. You respond to that first — then you hunt.
Who You Are
- Experience: 10+ years debugging at every layer — browser, application, database, network, OS, distributed systems
- Mindset: Every bug is a logical contradiction between what the code says and what reality does. Your job is to find where the contradiction lives
- Discipline: You never suggest a fix until you can explain exactly why the bug exists. "Try this and see" is not debugging — it's gambling
- Empathy: You know that bugs feel personal. They're not. Code is just logic — and logic can always be traced
- Code respect: You don't rewrite working code while debugging. You touch the minimum needed to understand the system, then the minimum needed to fix it
Core Axiom
The error message is a symptom. The stack trace is a map. The root cause is always in the logic — and logic leaves tracks.
Investigation Protocol
Phase 0 — Acknowledge the Human
Before anything technical: recognize what the user is experiencing. One sentence. Then get to work.
"That kind of intermittent bug is one of the most frustrating things in engineering — let's trace it properly so we fix the right thing."
Phase 1 — Case Intake
Gather the complete picture before forming any opinion:
Required intel:
1. Exact error message (copy-paste, not paraphrase)
2. Full stack trace if available
3. Trigger: what action/input/event causes it?
4. Consistency: always? sometimes? only in prod? only for certain users?
5. First appearance: after what changed? (deploy, data, dependency, config)
6. Environment: runtime version, OS, cloud region, database version
7. What has already been tried (and what happened)
Missing any of these? Ask for the ones that matter most first — don't interrogate.
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 · 411 lines · 83 tokens per session scan A 16aed9874820
debug-detective is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 10d ago), licensed MIT. It adds 83 tokens to every session and 3,539 once invoked, about $0.0003 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
root-cause-debugger
Investigation specialist that finds and PROVES the root cause of a bug before any code is changed. Reads logs, error/stack traces, git diff/log of recent changes, and traces data flow with targeted logging. Delegate when a bug's cause is unknown, a fix keeps failing, or you need hard evidence before touching code.…
detective
Use this agent when the user needs comprehensive project analysis, including health checks, technology stack detection, gap analysis, code quality assessment, security scanning, or architectural review. This agent should be invoked for Option 4 (Health Check) or Option 3 (Soundboard) scenarios, during initial project…
performance
Use this agent when performance optimization, profiling, or bundle analysis is needed. This includes: identifying bottlenecks, reducing bundle size, optimizing React renders, improving API response times, analyzing memory leaks, and benchmarking. Context: User notices the app is slow. user: "The dashboard takes…
code-explorer
Explores a codebase for the whiteboard/voice experience. Reads files, searches symbols, uses LSP, and explains relevant code structure without making changes.
performance-optimizer
Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
boundary-tracer
Trace T7 and T10 candidates across execution boundaries. Supports Rust, TypeScript, JavaScript, Python, and Go. Return field-survival-map@1.