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 plugin-conflictsgit 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/plugin-conflicts)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/plugin-conflicts"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/plugin-conflicts/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/plugin-conflicts"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/plugin-conflicts.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.00033 | $0.01029 |
| Opus 5.5 | $0.00013 | $0.00412 |
| Sonnet 5.5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
plugin-conflicts 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain 4: Plugin & Theme Conflict Resolution
4.1 Conflict Identification
- Hook priority collisions (same hook, same priority, conflicting behavior)
- JavaScript global namespace pollution
- CSS specificity wars between plugins/themes
- Shared library version conflicts (e.g., different jQuery UI versions)
- REST API route collisions
- Custom post type / taxonomy slug conflicts
- Cron job interference
- Session handling conflicts
- Object cache key collisions
4.2 Systematic Conflict Testing
- Binary search isolation: disable half the plugins, narrow down
- Theme switching test (to default theme like Twenty Twenty-Four)
- Browser console error analysis
- PHP error log analysis during activation/deactivation cycles
- Database state comparison before/after plugin activation
- REST API endpoint testing in isolation
4.3 Common Conflict Patterns
- Page builders fighting over editor hooks
- SEO plugins duplicating meta tags
- Security plugins blocking legitimate AJAX requests
- Caching plugins serving stale content for dynamic features
- Translation plugins conflicting with multilingual setups
- WooCommerce template overrides breaking after updates
- Multiple plugins enqueueing different versions of the same library
Systematic Conflict Resolution Process
Step 1: Reproduce the Issue
- Document exact steps to trigger the problem
- Note which user role experiences the issue
- Check browser console for JavaScript errors
- Check PHP error logs for warnings/fatals
- Test in incognito/private browsing mode (rules out caching)
Step 2: Binary Search Plugin Isolation
# Get list of active plugins
wp plugin list --status=active --field=name
# Disable all plugins
wp plugin deactivate --all
# Test if issue is resolved
# If yes, it's a plugin conflict. Proceed with binary search.
# Enable half the plugins
wp plugin activate plugin1 plugin2 plugin3
# Test again. If issue returns, conflict is in this half.
# If issue doesn't return, conflict is in the other half.
# Repeat until you isolate the conflicting plugin(s)
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 · 183 lines · 33 tokens per session scan A e56f682d8fea
plugin-conflicts is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (29 stars, last pushed 8mo ago), licensed MIT. It adds 33 tokens to every session and 1,029 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
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…
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.
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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.