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 dr-robert-li/cowork-wordpress-expert --skill diagnostic-config-securitygit clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expertWrote 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/dr-robert-li/cowork-wordpress-expert/diagnostic-config-security)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-config-security"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-config-security/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/dr-robert-li/cowork-wordpress-expert/diagnostic-config-security"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-config-security.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.00035 | $0.03454 |
| Opus 5 | $0.00017 | $0.01727 |
| Sonnet 5 | $0.00007 | $0.00691 |
| Haiku 4.5 | $0.00003 | $0.00345 |
Grade A, and why
diagnostic-config-security 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 12d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnostic Skill: wp-config.php Security
You analyze wp-config.php for critical security misconfigurations that expose the site to risk.
Scope: Critical Issues Only
Per user decision, this skill checks ONLY critical security issues. It explicitly DOES NOT check debatable settings like specific memory limits, table prefix recommendations on existing sites, or obscure hardening settings that vary by hosting environment.
What we check:
- WP_DEBUG set to true (Critical - leaks sensitive data in production)
- Default/empty authentication salts (Critical - session hijacking risk)
- DISALLOW_FILE_EDIT absent or false (Warning - allows theme/plugin editing)
- Default table prefix 'wp_' (Info only - noted but not critical)
- Database credentials in version control (Warning - credential exposure risk)
What we explicitly skip:
- Specific PHP memory limit values
- Table prefix change recommendations for existing sites
- Obscure wp-config hardening constants
- Database host recommendations
- SSL/HTTPS enforcement (separate check)
How It Works
- Load site connection details from
sites.json - Run checks REMOTELY via SSH (do NOT rely on local synced copy - wp-config.php may not be synced)
- Check for each security issue using SSH grep commands
- Generate structured findings with deterministic IDs
- Return findings as JSON array
Connection Details
# Read site profile
SITE_NAME="${1:-default-site}"
PROFILE=$(jq -r ".sites[\"$SITE_NAME\"]" sites.json)
HOST=$(echo "$PROFILE" | jq -r '.host')
USER=$(echo "$PROFILE" | jq -r '.user')
WP_PATH=$(echo "$PROFILE" | jq -r '.wp_path')
wp-config.php Location Handling
WordPress supports wp-config.php in two locations:
- Standard location:
{WP_PATH}/wp-config.php - One directory up:
{WP_PATH}/../wp-config.php(security by obscurity pattern)
Check both locations:
# Try standard location first
if ssh "${USER}@${HOST}" "test -f ${WP_PATH}/wp-config.php" 2>/dev/null; then
CONFIG_PATH="${WP_PATH}/wp-config.php"
elif ssh "${USER}@${HOST}" "test -f ${WP_PATH}/../wp-config.php" 2>/dev/null; then
CONFIG_PATH="${WP_PATH}/../wp-config.php"
else
# wp-config.php not found
echo "ERROR: wp-config.php not found"
exit 1
fi
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.
- 12d ago First seen · 303 lines · 35 tokens per session scan A 1509b4b22a2a
diagnostic-config-security is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 3,454 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…