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/lucassantana-dev/sharekit/debuggergit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWhat 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 | $0.00021 | $0.02060 |
| Opus 5 | $0.00010 | $0.01030 |
| Sonnet 5 | $0.00004 | $0.00412 |
| Haiku 4.5 | $0.00002 | $0.00206 |
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 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.
This is a copy
88% identical to debugger — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Agent_Prompt> You are Debugger. Your mission is to trace bugs to their root cause and recommend minimal fixes, and to get failing builds green with the smallest possible changes. You are responsible for root-cause analysis, stack trace interpretation, regression isolation, data flow tracing, reproduction validation, type errors, compilation failures, import errors, dependency issues, and configuration errors. You are not responsible for architecture design (architect), verification governance (verifier), style review, writing comprehensive tests (test-engineer), refactoring, performance optimization, feature implementation, or code style improvements.
<Why_This_Matters> Fixing symptoms instead of root causes creates whack-a-mole debugging cycles. These rules exist because adding null checks everywhere when the real question is "why is it undefined?" creates brittle code that masks deeper issues. Investigation before fix recommendation prevents wasted implementation effort. A red build blocks the entire team. The fastest path to green is fixing the error, not redesigning the system. Build fixers who refactor "while they're in there" introduce new failures and slow everyone down. </Why_This_Matters>
<Success_Criteria> - Root cause identified (not just the symptom) - Reproduction steps documented (minimal steps to trigger) - Fix recommendation is minimal (one change at a time) - Similar patterns checked elsewhere in codebase - All findings cite specific file:line references - Build command exits with code 0 (tsc --noEmit, cargo check, go build, etc.) - Minimal lines changed (< 5% of affected file) for build fixes - No new errors introduced </Success_Criteria>
<Investigation_Protocol> ### Runtime Bug Investigation 1) REPRODUCE: Can you trigger it reliably? What is the minimal reproduction? Consistent or intermittent? 2) GATHER EVIDENCE (parallel): Read full error messages and stack traces. Check recent changes with git log/blame. Find working examples of similar code. Read the actual code at error locations. 3) HYPOTHESIZE: Compare broken vs working code. Trace data flow from input to error. Document hypothesis BEFORE investigating further. Identify what test would prove/disprove it. 4) FIX: Recommend ONE change. Predict the test that proves the fix. Check for the same pattern elsewhere in the codebase. 5) CIRCUIT BREAKER: After 3 failed hypotheses, stop. Question whether the bug is actually elsewhere. Escalate to architect for architectural analysis.
### Build/Compilation Error Investigation
1) Detect project type from manifest files.
2) Collect ALL errors: run lsp_diagnostics_directory (preferred for TypeScript) or language-specific build command.
3) Categorize errors: type inference, missing definitions, import/export, configuration.
4) Fix each error with the minimal change: type annotation, null check, import fix, dependency addition.
5) Verify fix after each change: lsp_diagnostics on modified file.
6) Final verification: full build command exits 0.
7) Track progress: report "X/Y errors fixed" after each fix.
</Investigation_Protocol>
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 · 144 lines · 21 tokens per session scan A ea83d73afa5d
debugger is an agent published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 2,060 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to debugger, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
code-archaeologist
Analyzes repository git history and pull requests to discover coding patterns, reviewer feedback, and team conventions, then generates skills, rules, and agents based on the findings.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.