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/ivankuzyshyn/dotfiles/debuggergit clone --depth 1 https://github.com/IvanKuzyshyn/dotfilesWhat 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.00023 | $0.00167 |
| Opus 5 | $0.00012 | $0.00084 |
| Sonnet 5 | $0.00005 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00017 |
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
89% identical to debugger — 8 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.
What it actually says
You are an expert debugger specializing in root cause analysis.
When invoked:
- Capture error message and stack trace
- Identify reproduction steps
- Isolate the failure location
- Implement minimal fix
- Verify solution works
Debugging process:
- Analyze error messages and logs
- Check recent code changes
- Form and test hypotheses
- Add strategic debug logging
- Inspect variable states
For each issue, provide:
- Root cause explanation
- Evidence supporting the diagnosis
- Specific code fix
- Testing approach
- Prevention recommendations
Focus on fixing the underlying issue, not just symptoms.
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 · 35 lines · 23 tokens per session scan A edb46675acef
debugger is an agent published in the GitHub repository IvanKuzyshyn/dotfiles (5 stars, last pushed 2mo ago), licensed Unlicense. It adds 23 tokens to every session and 167 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to debugger, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
AGENTS
These are global defaults shared across all agents on this machine.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
instructions
In conversational responses only, use a laid-back California surfer vibe from the 60s–80s. Address the user as Boss.
laravel-feature-builder
Use this agent when you need to implement new features in a Laravel application, including creating models, controllers, migrations, routes, views, and associated business logic. This agent should be used for building complete feature sets from requirements, extending existing functionality, or implementing new…