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/jburlison/wowaddonapiagents/analyze-agent-overlapnpx skills add JBurlison/WoWAddonAPIAgents --skill analyze-agent-overlapgit clone --depth 1 https://github.com/JBurlison/WoWAddonAPIAgentsWrote 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/jburlison/wowaddonapiagents/analyze-agent-overlap)<a href="https://agentmods.dev/skills/jburlison/wowaddonapiagents/analyze-agent-overlap"><img src="https://agentmods.dev/badge/skills/jburlison/wowaddonapiagents/analyze-agent-overlap.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.00068 | $0.01278 |
| Opus 5 | $0.00034 | $0.00639 |
| Sonnet 5 | $0.00014 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
analyze-agent-overlap 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Agent Overlap
Detects redundancy, overlap, and potential conflicts between AI coding assistant customization files.
Provider Folder Reference
This skill works across multiple AI coding assistant providers:
| Provider | Base Folder |
|---|---|
| GitHub Copilot | .github/ |
| Claude Code | .claude/ |
| Codex | .codex/ |
| OpenCode | .config/opencode/ |
Throughout this document, <provider>/ represents your chosen provider's base folder.
When to Use
- Before creating a new agent, skill, prompt, or instruction
- When you suspect two agents are doing similar things
- To audit and consolidate your customization files
- When agent behaviors seem to conflict
Analysis Process
Step 1: Inventory Existing Items
Scan these locations (replace <provider>/ with actual folder):
<provider>/agents/*.md- All agent definitions (including.subagent.agent.md)<provider>/skills/*/SKILL.md- All skill definitions<provider>/prompts/*.prompt.md- All prompt templates<provider>/instructions/*.instructions.md- All instruction files
For each item, extract:
- Name: The identifier
- Purpose: What problem it solves (from description)
- Domain: What areas/topics it covers
- Triggers: Keywords or scenarios that activate it
- User-Invokable: Whether it's a user-facing agent or sub-agent
Step 2: Compare Against Proposed Item
When analyzing a proposed new item, compare:
Direct Overlap Indicators:
- Same or very similar name
- Same primary purpose statement
- Identical target domain
- Overlapping trigger keywords (>50% match)
Partial Overlap Indicators:
- Related but distinct purposes
- Some shared expertise areas
- Similar but different trigger scenarios
- Complementary functionality
No Overlap Indicators:
- Different domains entirely
- Non-overlapping use cases
- Distinct trigger keywords
Step 3: Detect Conflicts
Look for these conflict types:
Behavioral Conflicts:
- Two agents giving contradictory guidance for same scenario
- Instructions that override each other for same file patterns
- Skills that produce incompatible outputs
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 · 199 lines · 68 tokens per session scan A 8022f0e1c91a
analyze-agent-overlap is a skill published in the GitHub repository JBurlison/WoWAddonAPIAgents (43 stars, last pushed 6mo ago), licensed MIT. It adds 68 tokens to every session and 1,278 once invoked, about $0.0003 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…
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…