Borrowing it
Nothing to install: this file belongs to testdino-hq/testdino-mcp. 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/testdino-hq/testdino-mcp/main/.claude/skills/debug-tool/SKILL.mdgit clone --depth 1 https://github.com/testdino-hq/testdino-mcpWrote 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/skills/testdino-hq/testdino-mcp/debug-tool)<a href="https://agentmods.dev/skills/testdino-hq/testdino-mcp/debug-tool"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/debug-tool/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/skills/testdino-hq/testdino-mcp/debug-tool"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/debug-tool.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.00019 | $0.00759 |
| Opus 5.5 | $0.00008 | $0.00304 |
| Sonnet 5.5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
debug-tool 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug the tool issue: $ARGUMENTS
Do NOT guess. Trace systematically.
Phase 1 — Identify
- Which tool is affected?
- What is the expected behavior?
- What is the actual behavior? (error message, wrong data, empty response, crash)
Phase 2 — Trace the Request Lifecycle
Read the code for each layer and check for issues:
Layer 1: Tool Schema (src/tools/<category>/<tool>.ts)
- Is
namein the tool definition the same as the routing name inindex.ts? - Does
inputSchemamatch what the handler actually reads fromargs? - Are
requiredfields correctly listed? - Are
enumvalues complete?
Layer 2: Handler Logic
- Is
getApiKey(args)called correctly? - Are required params validated before use?
- Are type conversions correct? (
String(),Number()) - Is the params object passed to the endpoint builder correctly?
Layer 3: Endpoint URL (src/lib/endpoints.ts)
- Is the URL pattern correct? (
/api/mcp/${projectId}/...) - Are query params built correctly?
- Is
projectIdbeing destructured out before building query string? - Log the actual URL being built (add temporary
console.error)
Layer 4: HTTP Request (src/lib/request.ts)
- Is the right HTTP method used? (GET vs POST vs PATCH)
- Is
Content-Type: application/jsonbeing set? - Is the Authorization header present?
- For POST/PATCH: is the body being JSON.stringify'd?
Layer 5: Response Handling
- Does the API return
{ success, data }wrapper or direct data? - Is
response.okbeing checked? - Is the error text being read on failure?
- Is the response being JSON.stringify'd for the MCP return?
Phase 3 — Isolate
Once you've identified the suspect layer:
- Read the specific code carefully
- Check if other tools in the same category work (pattern comparison)
- If the issue is in
endpoints.ts, check the API docs or compare with working tools
Phase 4 — Fix & Verify
- Fix the root cause
- Run
npm run typecheck && npm run lint - If the tool's behavior or params changed, update
docs/TOOLS.md - Remove any temporary
console.errordebug lines
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 · 89 lines · 19 tokens per session scan A 08c7d34c6822
debug-tool is a skill published in the GitHub repository testdino-hq/testdino-mcp (10 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 759 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…