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 security-analysisgit 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/security-analysis)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/security-analysis"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/security-analysis/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/security-analysis"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/security-analysis.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.00036 | $0.01452 |
| Opus 5.5 | $0.00014 | $0.00581 |
| Sonnet 5.5 | $0.00007 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
security-analysis 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.
Domain 1: Security Audit
Evaluate the codebase and configuration against OWASP Top 10 and WordPress-specific vulnerability patterns.
1.1 Input Validation & Sanitization
- All user inputs pass through appropriate WordPress sanitization functions (
sanitize_text_field(),sanitize_email(),absint(),wp_kses(),wp_kses_post()) $_GET,$_POST,$_REQUEST,$_SERVER,$_COOKIEare never used directly without sanitization- Database inputs use
$wpdb->prepare()for all parameterized queries — no raw string concatenation in SQL - File upload validation checks MIME type, extension, and file size using WordPress APIs
esc_url()used for all URLs before output or redirect
1.2 Output Escaping
- All dynamic output escaped with context-appropriate functions:
- HTML context:
esc_html() - Attribute context:
esc_attr() - JavaScript context:
esc_js()orwp_json_encode() - URL context:
esc_url() - Translation with escaping:
esc_html__(),esc_html_e(),esc_attr__()
- HTML context:
- Template files reviewed for raw
echoof user-controlled data - No use of
eval(),assert(),preg_replace()withemodifier, orcreate_function()
1.3 Authentication & Authorization
- All AJAX handlers check
check_ajax_referer()or equivalent nonce verification - All form submissions verify nonces via
wp_verify_nonce() - REST API endpoints use
permission_callback(never__return_truefor sensitive operations) - Capability checks (
current_user_can()) before any privileged operation - No hardcoded credentials, API keys, or secrets in source code
- Authentication cookies use
httpOnly,Secure, andSameSiteflags where applicable
1.4 Cross-Site Request Forgery (CSRF)
- Every form includes
wp_nonce_field() - Every form handler verifies nonce before processing
- AJAX actions use
wp_create_nonce()/check_ajax_referer() - State-changing operations never triggered by GET requests alone
1.5 SQL Injection
- All database queries use
$wpdb->prepare()with proper placeholders (%s,%d,%f) - No direct concatenation of variables into SQL strings
LIKEqueries use$wpdb->esc_like()followed by$wpdb->prepare()- Custom table creation uses
dbDelta()with proper schema - No use of
query()with unsanitized input
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 · 36 tokens per session scan A d1d81361cc31
security-analysis is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (29 stars, last pushed 8mo ago), licensed MIT. It adds 36 tokens to every session and 1,452 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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…