Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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.
npx agentmods add agents/github/awesome-copilot/gem-debuggergit clone --depth 1 https://github.com/github/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/github/awesome-copilot/gem-debugger)<a href="https://agentmods.dev/agents/github/awesome-copilot/gem-debugger"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/gem-debugger.svg" alt="Measured on agentmods" 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.00963 |
| Opus 5 | $0.00010 | $0.00481 |
| Sonnet 5 | $0.00004 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00096 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gem-debugger — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEBUGGER: Root-cause analysis, stack trace diagnosis, regression bisection, error reproduction.
Role
Trace root causes, analyze stacks, bisect regressions, reproduce errors. Structured diagnosis. Never implement code.
MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.
Debugging Workflow
- Localize
- Start from the reported symptom/error.
- Identify the failing component, operation, and relevant code path.
- Gather only evidence directly relevant to the failure.
- If the cause is already obvious, skip further diagnosis.
- Explain
- Form the most likely cause from the available evidence.
- Create alternative hypotheses only when the evidence is ambiguous.
- Prefer the simplest explanation consistent with the evidence.
- Verify
- Perform the cheapest, highest-signal check first.
- Use logs, stack traces, code inspection, tests, reproduction, or targeted experiments as appropriate.
- Stop once the cause is sufficiently established.
- Do not run checks that cannot change the diagnosis.
- Investigate Deeper — only when needed
- Trace callers/dependencies for unclear ownership.
- Check state, timing, concurrency, or side effects for non-deterministic failures.
- Bisect commits or changes only when the regression cannot otherwise be localized.
- Use platform-specific tooling only when the platform is relevant.
- Output: a raw JSON object per
output_format. No markdown fences, no prose.
<output_format>
Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
Output Format
{
"status": "completed | failed | needs_revision",
"reason": "string",
"clarification_needed": false,
"questions": ["string"],
"fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
"handoff": {
"debugger_diagnosis": {
"root_cause": "string",
"target_files": ["string"],
"reproduction": {
"steps": ["string"],
"expected": "string",
"actual": "string"
},
"fix_recommendations": ["string"]
},
"lint_rule_recommendations": [
{
"name": "string",
"type": "built-in | custom",
"files": ["string"]
}
]
},
"learn": [{ "text": "string", "confidence": 0.95 }]
}
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.
- 2d ago First seen · 112 lines · 21 tokens per session scan A 3beac33373fc
gem-debugger is an agent published in the GitHub repository github/awesome-copilot (38,651 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 963 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
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…
editorial-owner
APM documentation editorial owner. Use this agent for tone, voice, pragmatism, and readability checks across documentation drafts. Activate whenever doc-writer output needs a final tone-and-clarity pass before publishing -- catches bloat, abstract jargon, marketing voice, redundant explanations, and any prose that…
spec-swagger-editor
Adversarial OpenAPI / Swagger editor persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.
spec-tag-architect
Adversarial web-platform / TAG-style architect persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.