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 report-generatorgit 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/report-generator)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/report-generator"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/report-generator/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/report-generator"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/report-generator.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.00045 | $0.02769 |
| Opus 5 | $0.00023 | $0.01385 |
| Sonnet 5 | $0.00009 | $0.00554 |
| Haiku 4.5 | $0.00005 | $0.00277 |
Grade A, and why
report-generator 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Generator Skill
This skill takes findings from all diagnostic skills (core-integrity, config-security, user-audit, version-audit, malware-scan, code-quality) and compiles them into a single structured markdown report with a health grade, executive summary, and categorized findings. It handles archive rotation so previous reports are preserved.
Section 1: Input
Finding Format
Accept findings from all diagnostic skills as JSON arrays. Each finding object has these fields:
{
"id": "SECR-CHECKSUMS-001",
"severity": "Critical",
"category": "Security",
"title": "Modified core file detected",
"summary": "A core WordPress file has been changed from its original version, which could indicate a security breach.",
"detail": "wp-includes/version.php has been modified. Checksum mismatch detected via wp core verify-checksums. File size differs from expected: 2847 bytes vs 2340 bytes expected.",
"location": "wp-includes/version.php",
"fix": "Run `wp core download --force` to restore original core files, or manually compare the file to identify intentional customizations."
}
Required Fields
| Field | Type | Description |
|---|---|---|
id |
string | Deterministic finding ID for cross-scan tracking |
severity |
string | One of: Critical, Warning, Info |
category |
string | One of: Security, Code Quality, Version & Compatibility, Suspicious Code |
title |
string | Short descriptive title |
summary |
string | One-sentence non-technical explanation |
detail |
string | Technical explanation with evidence |
location |
string | File path, file:line, or command reference |
fix |
string | Concrete remediation steps or code snippet |
Category Sources
Each category maps to specific diagnostic skills:
- Security: Findings from
diagnostic-core-integrity,diagnostic-config-security,diagnostic-user-audit - Code Quality: Findings from
diagnostic-code-quality - Version & Compatibility: Findings from
diagnostic-version-audit - Suspicious Code: Findings from
diagnostic-malware-scan
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 · 321 lines · 45 tokens per session scan A 4e3e3f7625fe
report-generator is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 2,769 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…
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…
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…
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…