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 agentmods add skills/dr-robert-li/cowork-wordpress-expert/plugin-conflictsnpx 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.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.01029 |
| Opus 5 | $0.00016 | $0.00515 |
| Sonnet 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 5d 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.
- 5d 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 (28 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 1,029 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…