scan-reviewer

scan-reviewer is a skill for Claude Code from dr-robert-li/cowork-wordpress-expert. It costs 27 tokens per session (2,243 once invoked), scanned A, original, MIT.

A checker for completed diagnostic scans, reviewing whether the investigation answered the user's original concern. A diagnostic scan is a structured search for causes or problems.

In plain words
What is it for?
Use it to verify scan coverage, compare findings with the original concern, and check that the final diagnostic report is consistent.
Why use it?
It catches reports that ran checks but missed the actual question, or that contain findings that do not agree with one another.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it to verify scan coverage, compare findings with the original concern, and check that the final diagnostic report is consistent.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dr-robert-li/cowork-wordpress-expert/scan-reviewer
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 scan-reviewer
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 scan-reviewer

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/scan-reviewer"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/scan-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,243 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00027 $0.02243
Opus 5 $0.00014 $0.01122
Sonnet 5 $0.00005 $0.00449
Haiku 4.5 $0.00003 $0.00224

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

Security

Grade A, and why

scan-reviewer 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 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.

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.

skills/scan-reviewer/SKILL.md · 275 lines

How it starts

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

Scan Reviewer Skill: Findings Verification

You verify that a completed diagnostic scan actually addressed the user's original concern. This is a goal-backward check: start from what the user wanted to know, and verify the findings answer it.

Philosophy

A scan that runs all skills but misses the user's actual concern is a failed scan. This skill catches that gap before the user sees the report.

Section 1: Input

Load the investigation context and combined findings.

SITE_NAME="${1:-default-site}"
MEMORY_DIR="memory/${SITE_NAME}"

# Load the active case (what the user asked about)
ACTIVE_CASE="${MEMORY_DIR}/active-case.json"
if [ -f "$ACTIVE_CASE" ]; then
  CONCERN_SUMMARY=$(jq -r '.concern.summary' "$ACTIVE_CASE")
  CONCERN_TYPE=$(jq -r '.concern.type' "$ACTIVE_CASE")
  URGENCY=$(jq -r '.concern.urgency' "$ACTIVE_CASE")
  PRIORITY_SKILLS=$(jq -r '.diagnostic_focus.priority_skills[]' "$ACTIVE_CASE")
  FOCUS_AREAS=$(jq -r '.diagnostic_focus.focus_areas[]' "$ACTIVE_CASE")
else
  # No active case — this is a standard /diagnose run, not /investigate
  # Apply basic verification only
  CONCERN_SUMMARY="General diagnostic scan"
  CONCERN_TYPE="general"
  URGENCY="routine"
fi

# Load combined findings (passed as argument or read from memory)
# COMBINED_FINDINGS is the JSON array of all findings from all skills

Section 2: Verification Checks

Check 1: Concern Addressal

Do the findings address what the user actually asked about?

Process:

  1. Extract the concern type and keywords from active-case.json
  2. Map concern type to expected finding categories
  3. Check if findings exist in those categories

Concern-to-category mapping:

Concern Type Expected Categories Minimum Expected
security Security, Suspicious Code At least 1 finding OR explicit "no issues found"
performance Code Quality At least 1 finding OR explicit "no issues found"
code-quality Code Quality, Suspicious Code At least 1 finding OR explicit "no issues found"
updates Version & Compatibility At least 1 finding OR explicit "no issues found"
general Any Findings in at least 2 categories

Read the full file on GitHub · 275 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 · 275 lines · 27 tokens per session scan A 1148eab3b043

Subscribe to this mod's changes

scan-reviewer is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 2,243 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-30.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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.

emdash-cms/emdash · 43 tokens

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.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens