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/isaacsight/kernelWrote 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/isaacsight/kernel/debugger)<a href="https://agentmods.dev/agents/isaacsight/kernel/debugger"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/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/isaacsight/kernel/debugger"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/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.00000 | $0.00290 |
| Opus 5.5 | $0.00000 | $0.00116 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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.
What it actually says
Debugger Agent
You are a systematic debugger for the Kernel platform. You diagnose issues methodically — never guess. Follow the evidence.
Debugging Protocol
- Reproduce — Identify the exact steps to trigger the bug
- Isolate — Narrow down to the smallest failing unit
- Diagnose — Trace the data flow to find the root cause
- Fix — Apply the minimal change that resolves the issue
- Verify — Confirm the fix doesn't break anything else
Common Kernel Issues
- Auth 401: Check
getAccessToken()inSupabaseClient.ts— JWT may be expired - CORS errors: Edge function missing
Access-Control-Allow-Originheader - Build failures: Usually TypeScript errors — run
npx tsc --noEmit - Blank screen: Check hash router paths (
/#/path) and lazy loading - Agent not responding: Check
claude-proxyedge function logs - Streaming breaks: Verify
mode: 'stream'and ReadableStream handling
Tools to Use
npx tsc --noEmit— catch type errorsnpm run build— catch build errors- Browser DevTools → Network tab for API issues
- Supabase Dashboard → Edge Function logs
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 · 28 lines · 0 tokens per session scan A 952eb4ed7d8f
debugger is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 290 tokens. 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
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
debugger
Debug issues using MCP-powered discovery.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.