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 TrueClicks/claude-plugins --skill skill-017-negative-keyword-conflict-detectiongit clone --depth 1 https://github.com/TrueClicks/claude-pluginsWrote 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/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection)<a href="https://agentmods.dev/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection/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/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection"><img src="https://agentmods.dev/badge/skills/trueclicks/claude-plugins/skill-017-negative-keyword-conflict-detection.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.00648 |
| Opus 5 | $0.00016 | $0.00324 |
| Sonnet 5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
skill-017-negative-keyword-conflict-detection 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 12d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 017: Negative Keyword Conflict Detection
Purpose
Identify negative keywords that are blocking or could block desired active keywords, causing ads not to show for intended queries. Negative/positive conflicts can silently suppress valuable traffic.
Data Requirements
Data Source: Standard
Standard Data:
data/account/shared_negative_lists.md- Shared negative keyword listsdata/account/campaigns/*/negative_keywords.md- Campaign-level negativesdata/account/campaigns/*/*/negative_keywords.md- Ad group-level negativesdata/account/campaigns/*/*/keywords.md- Active positive keywords
Reference GAQL:
SELECT
campaign.name,
ad_group.name,
ad_group_criterion.keyword.text,
ad_group_criterion.keyword.match_type,
ad_group_criterion.negative
FROM keyword_view
WHERE ad_group_criterion.status = 'ENABLED'
Use /google-ads:get-custom if you need to include shared set data.
Analysis Steps
- Build negative inventory: Compile all negatives with scope (shared list, campaign, ad group) and match type
- Build positive inventory: Compile all active keywords with match type and location
- Detect direct conflicts: Check if negatives would block positives (exact blocks same text, phrase blocks containing text, broad blocks all-words match)
- Check hierarchy conflicts: Campaign negatives blocking ad group keywords; shared list blocking campaign keywords
- Assess severity: Complete block (keyword fully suppressed) vs. partial/potential block
Thresholds
| Condition | Severity |
|---|---|
| Negative exactly matches active keyword | Critical |
| Phrase negative contains words from active keyword | Critical |
| Shared list negative blocks campaign keyword | Critical |
| Broad negative words all appear in active keyword | Warning |
| Close variant match possible | Info |
Output
Use Short format by default. Use Detailed if user requests comprehensive analysis.
Short:
## Negative Conflict Detection Audit
**Account:** [Name] | **Conflicts Found:** [X]
### Critical ([Count])
- **"[negative]"** (phrase) blocks **"[keyword]"** → Remove negative or use exact match
- **Shared list** "[list]" blocks campaign keyword → Remove from list
### Warnings ([Count])
- **"[negative]"** (broad) may block **"[keyword]"** → Review and test
### Recommendations
1. Remove or modify [X] blocking negatives
2. Change [X] phrase negatives to exact match
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.
- 12d ago First seen · 78 lines · 33 tokens per session scan A 415b430e83a1
skill-017-negative-keyword-conflict-detection is a skill published in the GitHub repository TrueClicks/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 648 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-31.
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…