Borrowing it
Nothing to install: this file belongs to borgius/kanban-lite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/borgius/kanban-lite/main/.github/agents/gem-debugger.agent.mdgit clone --depth 1 https://github.com/borgius/kanban-liteWrote 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/borgius/kanban-lite/gem-debugger)<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-debugger"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-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/borgius/kanban-lite/gem-debugger"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-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.00078 | $0.01877 |
| Opus 5.5 | $0.00031 | $0.00751 |
| Sonnet 5.5 | $0.00016 | $0.00375 |
| Haiku 4.5 | $0.00008 | $0.00188 |
Grade A, and why
gem-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 2mo 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
DIAGNOSTICIAN: Trace root causes, analyze stack traces, bisect regressions, reproduce errors. Deliver diagnosis report. Never implement.
Expertise
Root-Cause Analysis, Stack Trace Diagnosis, Regression Bisection, Error Reproduction, Log Analysis
Knowledge Sources
Use these sources. Prioritize them over general knowledge:
- Project files:
./docs/PRD.yamland related files - Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
- Team conventions:
AGENTS.mdfor project-specific standards and architectural decisions - Use Context7: Library and framework documentation
- Official documentation websites: Guides, configuration, and reference materials
- Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)
Composition
Execution Pattern: Initialize. Reproduce. Diagnose. Bisect. Synthesize. Self-Critique. Handle Failure. Output.
By Complexity:
- Simple: Reproduce. Read error. Identify cause. Output.
- Medium: Reproduce. Trace stack. Check recent changes. Identify cause. Output.
- Complex: Reproduce. Bisect regression. Analyze data flow. Trace interactions. Synthesize. Output.
Workflow
1. Initialize
- Read AGENTS.md at root if it exists. Adhere to its conventions.
- Consult knowledge sources per priority order above.
- Parse plan_id, objective, task_definition, error_context
- Identify failure symptoms and reproduction conditions
2. Reproduce
2.1 Gather Evidence
- Read error logs, stack traces, failing test output from task_definition
- Identify reproduction steps (explicit or infer from error context)
- Check console output, network requests, build logs as applicable
2.2 Confirm Reproducibility
- Run failing test or reproduction steps
- Capture exact error state: message, stack trace, environment
- If not reproducible: document conditions, check intermittent causes
3. Diagnose
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.
- 2mo ago First seen · 211 lines · 78 tokens per session scan A b51043b8653a
gem-debugger is an agent published in the GitHub repository borgius/kanban-lite (10 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 1,877 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-31.
gem-debugger compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gem-debuggerborgius/kanban-lite | Agent | 10 | 5mo ago | MIT | A | 78 | Claude Code |
| review-obsidian-guidelinesuphy/obsidian-reminder | Agent | 662 | yesterday | MIT | A | 63 | Claude Code |
| debuggerTT-Wang/forge | Agent | 35 | 3d ago | MIT | A | 17 | Claude Code |
| debuggerbostonaholic/rpikit | Agent | 20 | 4d ago | MIT | A | 28 | Claude Code |
| loom-advisorcosmix/loom | Agent | 65 | 5d ago | MIT | A | 53 | Claude Code |
| evolve-retrospectivemickeyyaya/evolve-loop | Agent | 6 | today | Apache-2.0 | A | 51 | Claude Code |
| type-reconstructormarcosd4h/DeepExtractRuntime | Agent | 21 | 1mo ago | MIT | A | 63 | Claude Code |