Borrowing it
Nothing to install: this file belongs to abdullah1854/MCPGateway. 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/abdullah1854/MCPGateway/main/.agents/skills/debugging/SKILL.mdgit clone --depth 1 https://github.com/abdullah1854/MCPGatewayWrote 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/abdullah1854/mcpgateway/debugging)<a href="https://agentmods.dev/skills/abdullah1854/mcpgateway/debugging"><img src="https://agentmods.dev/badge/skills/abdullah1854/mcpgateway/debugging/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/abdullah1854/mcpgateway/debugging"><img src="https://agentmods.dev/badge/skills/abdullah1854/mcpgateway/debugging.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.00063 | $0.05830 |
| Opus 5.5 | $0.00025 | $0.02332 |
| Sonnet 5.5 | $0.00013 | $0.01166 |
| Haiku 4.5 | $0.00006 | $0.00583 |
Grade A, and why
debugging 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 1mo 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 — 732 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Protocol (v2 -- Friction-Hardened)
Built from 169 real sessions. Addresses 38 "wrong approach" events, 30 "buggy code" events, 17 "misunderstood request" events. Every rule below exists because it was violated in production.
When This Skill Activates
- "Debug this", "fix this bug", "not working"
- Error messages, stack traces
- "Undefined", "null", "crash", "fails"
- Unexpected behavior
- Performance issues
- Database query returning wrong data
- "Who changed X?" / audit trail questions
STOP-THINK-ACT Protocol (MANDATORY -- Execute Before EVERY Action)
Origin: 38 sessions had "wrong approach" friction -- Claude jumped to the wrong tool, wrong file, or wrong strategy before understanding context. This protocol is non-negotiable.
STOP -- Before writing code, running commands, or choosing an approach:
| Check | Question | If Unclear |
|---|---|---|
| System | Which system/environment is this? Local app? Remote server? Database? | ASK the user. Never assume. |
| Output format | What format does the user want? SQL? Code fix? Plan document? Working code? | ASK if ambiguous. |
| Target file | Am I editing the right file? Local vs remote? Config vs code? Is there a secondary config file? | Verify path before editing. |
| Database | Which database connection? Which server? | Confirm before querying. |
| Branch/Env | Am I on the right branch? Right environment? | Check with git branch or ask. |
THINK -- Before stating conclusions:
| Check | Question | Violation Example |
|---|---|---|
| Evidence | Do I have concrete evidence? | Saying "User X broke this" without a git blame diff |
| Schema | Have I verified actual schemas via MCP? | Assuming a column TransactionDate exists when it's actually TRANSDATE |
| Scope | Am I about to explore when I should execute, or code when asked for a plan? | Spending 45 minutes reading files when user wants a one-line fix |
| Attribution | Am I about to blame someone/something without proof? | "This was probably caused by the last deployment" -- prove it |
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.
- 1mo ago First seen · 732 lines · 63 tokens per session scan A c6a6609eaab1
debugging is a skill published in the GitHub repository abdullah1854/MCPGateway (17 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 5,830 once invoked, about $0.0003 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-30.
Other skills, from other repositories
triage
Diagnose and fix broken MCP servers in mcptoon — doctor, health, per-server probes, and the common failure playbook.
instance-performance-triage
Answer "the instance is slow" or "my nightly job never ran" from ServiceNow's own telemetry — transaction logs, syslog, systrigger, progress workers, execution trackers — instead of ad-hoc scripts that add to the load.
change-rollback
Undo a change already written to a ServiceNow instance — recover the prior payload from sysupdateversion, write it back without corrupting it, and know which damage update set back-out, Deleted Records, or nothing at all can reverse.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
blast-radius
Trace ServiceNow configuration dependencies — what artifacts touch a given field, what calls a script include, table/app-level config inventory. Use before deletes, renames, or refactors.