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 TheophilusChinomona/claude-openclaw-plugin --skill openclaw-agent-debuggergit clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginWrote 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/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-debugger)<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-debugger"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-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/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-debugger"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-agent-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.00000 | $0.03037 |
| Opus 5 | $0.00000 | $0.01519 |
| Sonnet 5 | $0.00000 | $0.00607 |
| Haiku 4.5 | $0.00000 | $0.00304 |
Grade A, and why
openclaw-agent-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 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.
How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Agent Debugger
Diagnose OpenClaw problems systematically — from symptom to root cause to exact fix.
Diagnostic Philosophy
Every OpenClaw problem has a finite set of root causes. This skill works through them systematically rather than guessing. It always starts with the most likely cause for the reported symptom and works outward.
Stage 1: Symptom Triage
Classify the reported problem into one of these categories:
| Symptom | Most Likely Root Cause | First Check |
|---|---|---|
| Agent not responding at all | Gateway down / channel disconnected | openclaw gateway status |
| Wrong agent responding | Binding order wrong / default agent incorrect | Check bindings in openclaw.json |
| Heartbeat stopped firing | every: "0m" / activeHours window / no heartbeat block on any agent |
Check heartbeat config |
| Heartbeat fires but no message sent | target: "none" or target resolves to nothing |
Check target + to fields |
| Cron job not running | cron.enabled: false / wrong timezone / job disabled |
openclaw cron list |
| Cron job runs but no delivery | delivery.mode: "none" / wrong channel target |
Check job delivery config |
| Gateway won't start | Config validation error / port conflict / auth missing | openclaw doctor |
| Model errors | Wrong model string format / missing API key / rate limit | Check model.primary format |
| Memory not persisting | Workspace path wrong / file permissions / session type | Check workspace config |
| Channel offline | Auth expired / bot token invalid / account not linked | openclaw channels status --probe |
| "Unauthorized" on connect | Auth token mismatch | Check OPENCLAW_GATEWAY_TOKEN |
| Multiple agents, routing broken | Binding specificity order wrong | Check binding priority order |
Stage 2: Gather Diagnostics
Request or run these commands in order. Each is a gate — stop if you find the problem.
Gate 1: Gateway health
openclaw gateway status # Is Gateway running?
openclaw gateway status --deep # Detailed health
openclaw status # Quick overview
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 · 390 lines · 0 tokens per session scan A 53c3a73259b5
openclaw-agent-debugger is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,037 tokens. 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
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.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.