diagnostic-core-integrity

diagnostic-core-integrity is a skill for Claude Code from dr-robert-li/cowork-wordpress-expert. It costs 24 tokens per session (2,456 once invoked), scanned B, original, MIT.

A WordPress diagnostic that compares core files with official WordPress.org checksums, which are expected file fingerprints.

In plain words
What is it for?
Use it to verify a site's core installation over SSH and return structured findings about mismatched files.
Why use it?
It can reveal changed, corrupted, or potentially compromised WordPress core files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the wordpress-expert plugin — 54 skills shipped together

Good fit Use it to verify a site's core installation over SSH and return structured findings about mismatched files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity
Install

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.

Any agent
npx skills add dr-robert-li/cowork-wordpress-expert --skill diagnostic-core-integrity
Clone the repo
git clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expert

Made for: Claude Code.

Or install wordpress-expert, the plugin that ships this one along with the rest of its 54 skills.

Wrote 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.

agentmods badge for diagnostic-core-integrity

README.md
[![agentmods](https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity/github.svg)](https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity)
Your own site
<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity/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.

agentmods 80×15 button for diagnostic-core-integrity

Your own site · 80×15
<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/diagnostic-core-integrity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,456 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.02456
Opus 5 $0.00012 $0.01228
Sonnet 5 $0.00005 $0.00491
Haiku 4.5 $0.00002 $0.00246

Measured 11d ago against content hash b470d56a9db8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

diagnostic-core-integrity scanned grade B with 2 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 11d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

"fix": "Install WP-CLI by running: `curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar && chmod +x wp-cli.phar && sudo mv wp-cli.phar /usr/local/bin/wp`. Then update the site profile in sit

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

"fix": "Install WP-CLI by running: `curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar && chmod +x wp-cli.phar && sudo mv wp-cli.phar /usr/local/bin/wp`. Then update the site profile in sit
skills/diagnostic-core-integrity/SKILL.md · 270 lines

How it starts

The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Diagnostic Skill: Core File Integrity

You verify WordPress core file integrity by checking all core files against official WordPress.org checksums using WP-CLI.

How It Works

  1. Load site connection details from sites.json
  2. Execute wp core verify-checksums over SSH
  3. Parse output to detect modified files
  4. Generate structured findings for each issue
  5. Return findings as JSON array

Connection Details

Load the site profile from sites.json:

# Read site profile (site name provided by user)
SITE_NAME="${1:-default-site}"
PROFILE=$(jq -r ".sites[\"$SITE_NAME\"]" sites.json)

# Extract connection details
HOST=$(echo "$PROFILE" | jq -r '.host')
USER=$(echo "$PROFILE" | jq -r '.user')
WP_PATH=$(echo "$PROFILE" | jq -r '.wp_path')
WP_CLI_PATH=$(echo "$PROFILE" | jq -r '.wp_cli_path')

SSH Command Execution

Execute WP-CLI verify-checksums with proper error handling:

# Run checksum verification over SSH
ssh -o BatchMode=yes \
    -o ConnectTimeout=10 \
    "${USER}@${HOST}" \
    "cd ${WP_PATH} && ${WP_CLI_PATH} core verify-checksums --format=json" 2>&1

Note: Use --format=json for structured output. However, WP-CLI may return plain text on success or errors.

Outcome Handling

Outcome A: All files verified (Success)

Indicators:

  • Exit code: 0
  • Output: Empty or "Success: WordPress installation verifies against checksums."

Action: Generate Info finding indicating site is secure.

Finding:

{
  "id": "SECR-CHECKSUMS-OK",
  "severity": "Info",
  "category": "Security",
  "title": "WordPress core files verified",
  "summary": "All WordPress core files match official checksums from WordPress.org",
  "detail": "WP-CLI checksum verification completed successfully. No modified or suspicious core files detected.",
  "location": "WordPress core installation",
  "fix": "No action required. Core files are intact."
}

Outcome B: Modified files detected

Indicators:

  • Exit code: Non-zero (typically 1)
  • Output contains: "Warning: File doesn't verify against checksum" or JSON array of modified files

Read the full file on GitHub · 270 lines

Changes

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.

  1. 11d ago First seen · 270 lines · 24 tokens per session scan B b470d56a9db8

Subscribe to this mod's changes

diagnostic-core-integrity is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 2,456 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens