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 stuartshields/claude-setup --skill debug-wpgit clone --depth 1 https://github.com/stuartshields/claude-setupWrote 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/stuartshields/claude-setup/debug-wp)<a href="https://agentmods.dev/skills/stuartshields/claude-setup/debug-wp"><img src="https://agentmods.dev/badge/skills/stuartshields/claude-setup/debug-wp/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/stuartshields/claude-setup/debug-wp"><img src="https://agentmods.dev/badge/skills/stuartshields/claude-setup/debug-wp.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.00022 | $0.01777 |
| Opus 5.5 | $0.00009 | $0.00711 |
| Sonnet 5.5 | $0.00004 | $0.00355 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
debug-wp 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: debug-wp
When to Use
Use this skill when diagnosing any WordPress problem - white screen of death, plugin conflicts, 500 errors, broken layouts, admin lockouts, performance issues, migration failures, cron problems, or any "it was working yesterday" scenario.
Do NOT jump to solutions. Always complete the triage interview first.
Use $ARGUMENTS as the initial symptom description. If empty, ask the user to describe the issue.
Procedure
Phase 1: Triage Interview
Ask questions in this order. Use AskUserQuestion where possible for structured input. Stop early if the user provides enough context to confidently diagnose (including any symptom passed via $ARGUMENTS).
1. Symptom
- What exactly is broken? (white screen, error message, wrong content, slow load, redirect loop, etc.)
- Is there a specific error message or error code? (copy/paste the exact text)
- Does it affect the frontend, the admin (
/wp-admin), or both?
2. Trigger
- When did this start? (after an update, migration, hosting change, new plugin, code edit)
- What was the last change made before the issue appeared?
- Was anything recently updated? (WordPress core, theme, plugin, PHP version, server config)
3. Scope
- Does it affect all pages or specific pages/post types?
- Does it affect all users or only logged-in / logged-out users?
- Does it affect all browsers / devices or specific ones?
- Is this a single site or WordPress Multisite?
4. Environment
- WordPress version
- PHP version
- Hosting type (shared, VPS, managed WP like WP Engine / Kinsta / Flywheel, local dev)
- Active theme (and whether it's a child theme)
- Recently activated or deactivated plugins
- Caching layers (page cache plugin, object cache like Redis/Memcached, CDN like Cloudflare)
- Is
WP_DEBUGenabled?
5. Logs & Evidence
- Ask for
wp-content/debug.logorcontent/debug.logcontents (ifWP_DEBUG_LOGis enabled) - Ask for server error log snippets (Apache
error_log, Nginxerror.log, or hosting panel logs) - Ask for browser console errors (if frontend issue)
- Ask for relevant screenshots if the issue is visual
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 · 143 lines · 22 tokens per session scan A b9058f983d29
debug-wp is a skill published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,777 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
debug
Instrument web/web-app code with structured debug logging via a global variable (window.debuglogs). Produces a clean JSON timeline for reproducing and diagnosing bugs. Use when user wants to debug a feature or track down a bug.
transcript-grep
Search a Claude Code session transcript for a string or regex pattern and show every matching message with surrounding context. Reads /api/sessions/:id/transcript and resolves sessions via /api/sessions?limit= from the Agent Monitor dashboard. Use when hunting for a specific message, prompt, tool call, or error inside…
anomaly-alert
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error…
regression-watch
Detect quality and efficiency regressions over time using Agent Monitor data — rising error rate (APIError events), falling cache hit rate, growing compaction frequency, and climbing cost-per-session. Splits history into an earlier baseline window and a recent window and reports which metrics are getting worse, by how…
hook-inventory
Inventory hooks across the user, project, and project-local settings plus the /.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook…
event-trace
Trace the full event chain for one Claude Code session into an ordered timeline of every event type with toolname and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?sessionid= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step…