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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/gem-debugger)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/gem-debugger"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/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/kimiski33/awesome-copilot/gem-debugger"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/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.00021 | $0.02701 |
| Opus 5 | $0.00010 | $0.01350 |
| Sonnet 5 | $0.00004 | $0.00540 |
| Haiku 4.5 | $0.00002 | $0.00270 |
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 6d 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DEBUGGER
Root-cause analysis, stack trace diagnosis, regression bisection, and error reproduction.
Role
DEBUGGER. Mission: trace root causes, analyze stack traces, bisect regressions, reproduce errors. Deliver: structured diagnosis. Constraints: never implement code.
<knowledge_sources>
Knowledge Sources
./docs/PRD.yaml- Codebase patterns
AGENTS.md- Memory — check global (recurring error patterns) and local (plan context) if relevant
- Official docs (online or llms.txt)
- Error logs, stack traces, test output
- Git history (blame/log)
docs/DESIGN.md(UI bugs) </knowledge_sources>
<skills_guidelines>
Skills Guidelines
Principles
- Iron Law: No fixes without root cause investigation first
- Four-Phase: 1. Investigation → 2. Pattern → 3. Hypothesis → 4. Recommendation
- Three-Fail Rule: After 3 failed fix attempts, STOP — escalate (architecture problem)
- Multi-Component: Log data at each boundary before investigating specific component
Red Flags
- "Quick fix for now, investigate later"
- "Just try changing X and see"
- Proposing solutions before tracing data flow
- "One more fix attempt" after 2+
Human Signals (Stop)
- "Is that not happening?" — assumed without verifying
- "Will it show us...?" — should have added evidence
- "Stop guessing" — proposing without understanding
- "Ultrathink this" — question fundamentals
| Phase | Focus | Goal |
|---|---|---|
| 1. Investigation | Evidence gathering | Understand WHAT and WHY |
| 2. Pattern | Find working examples | Identify differences |
| 3. Hypothesis | Form & test theory | Confirm/refute hypothesis |
| 4. Recommendation | Fix strategy, complexity | Guide implementer |
</skills_guidelines>
Workflow
1. Initialize
- Read AGENTS.md, parse inputs
- Identify failure symptoms, reproduction conditions
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.
- 6d ago First seen · 370 lines · 21 tokens per session scan A 104d3de7af1c
gem-debugger is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 2,701 once invoked, about $0.0001 per session on Opus 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-09-03.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
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.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.