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 skills add WarrenZhu050413/Warren-Claude-Code-Plugin-Marketplace --skill claude-sdk-debuggit clone --depth 1 https://github.com/WarrenZhu050413/Warren-Claude-Code-Plugin-MarketplaceWrote 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/warrenzhu050413/warren-claude-code-plugin-marketplace/claude-sdk-debug)<a href="https://agentmods.dev/skills/warrenzhu050413/warren-claude-code-plugin-marketplace/claude-sdk-debug"><img src="https://agentmods.dev/badge/skills/warrenzhu050413/warren-claude-code-plugin-marketplace/claude-sdk-debug/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/warrenzhu050413/warren-claude-code-plugin-marketplace/claude-sdk-debug"><img src="https://agentmods.dev/badge/skills/warrenzhu050413/warren-claude-code-plugin-marketplace/claude-sdk-debug.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.00024 | $0.01792 |
| Opus 5 | $0.00012 | $0.00896 |
| Sonnet 5 | $0.00005 | $0.00358 |
| Haiku 4.5 | $0.00002 | $0.00179 |
Grade A, and why
Claude SDK 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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 241 lines · 24 tokens per session scan A 5431eb76ed7d
Claude SDK Debugging is a skill published in the GitHub repository WarrenZhu050413/Warren-Claude-Code-Plugin-Marketplace (7 stars, last pushed 7mo ago), with no licence file. It adds 24 tokens to every session and 1,792 once invoked, about $0.0001 per session on Opus 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
session-health-probe
Runtime daemon + live-session liveness probe (zero-LLM, deterministic): daemon up, sessions progressing (not wedged — RP41 double-signal), RSS under budget, no unrecovered failure events, deployed commit == expected. Snapshot now; runs as a 15-min job; red → Slack.
swarm-daemon
Manage the SwarmAI launchd daemon: status, stop, start, restart, deploy, logs, and health verification. Replaces manual launchctl and dev.sh daemon commands with structured per-step execution. TRIGGER: "daemon status", "restart daemon", "daemon logs", "stop daemon". NOT FOR: sswarm-build, sswarm-hive use cases.
swarm-ci
Check SwarmAI GitHub Actions CI status: list recent runs, diagnose failures, and summarize health. Replaces ad-hoc gh run commands with structured output. TRIGGER: "CI status", "check CI", "is CI green", "CI failures". NOT FOR: pytest use cases.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.