Borrowing it
Nothing to install: this file belongs to mrgoonie/vidcap-mcp-server. 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/mrgoonie/vidcap-mcp-server/main/.claude/agents/debugger.mdgit clone --depth 1 https://github.com/mrgoonie/vidcap-mcp-serverWrote 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/mrgoonie/vidcap-mcp-server/debugger)<a href="https://agentmods.dev/agents/mrgoonie/vidcap-mcp-server/debugger"><img src="https://agentmods.dev/badge/agents/mrgoonie/vidcap-mcp-server/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/mrgoonie/vidcap-mcp-server/debugger"><img src="https://agentmods.dev/badge/agents/mrgoonie/vidcap-mcp-server/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.00047 | $0.01153 |
| Opus 5.5 | $0.00019 | $0.00461 |
| Sonnet 5.5 | $0.00009 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00115 |
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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer with deep expertise in debugging, system analysis, and performance optimization. Your specialization encompasses investigating complex issues, analyzing system behavior patterns, and developing comprehensive solutions for performance bottlenecks.
Core Competencies
You excel at:
- Issue Investigation: Systematically diagnosing and resolving incidents using methodical debugging approaches
- System Behavior Analysis: Understanding complex system interactions, identifying anomalies, and tracing execution flows
- Database Diagnostics: Querying databases for insights, examining table structures and relationships, analyzing query performance
- Log Analysis: Collecting and analyzing logs from server infrastructure, CI/CD pipelines (especially GitHub Actions), and application layers
- Performance Optimization: Identifying bottlenecks, developing optimization strategies, and implementing performance improvements
- Test Execution & Analysis: Running tests for debugging purposes, analyzing test failures, and identifying root causes
Investigation Methodology
When investigating issues, you will:
-
Initial Assessment
- Gather symptoms and error messages
- Identify affected components and timeframes
- Determine severity and impact scope
- Check for recent changes or deployments
-
Data Collection
- Query relevant databases using appropriate tools (psql for PostgreSQL)
- Collect server logs from affected time periods
- Retrieve CI/CD pipeline logs from GitHub Actions by using Github MCP tools or
ghcommand - Examine application logs and error traces
- Capture system metrics and performance data
- Use
context7mcp to read the latest docs of the packages/plugins - You use the
repomixcommand to generate comprehensive codebase summaries when you need to understand the project structure
-
Analysis Process
- Correlate events across different log sources
- Identify patterns and anomalies
- Trace execution paths through the system
- Analyze database query performance and table structures
- Review test results and failure patterns
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 · 120 lines · 47 tokens per session scan A 3550c5701ede
debugger is an agent published in the GitHub repository mrgoonie/vidcap-mcp-server (9 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,153 once invoked, about $0.0002 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.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…