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 Shipper-dot-now/conqueror-skills --skill conqueror-keyword-clusteringgit clone --depth 1 https://github.com/Shipper-dot-now/conqueror-skillsWrote 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/shipper-dot-now/conqueror-skills/conqueror-keyword-clustering)<a href="https://agentmods.dev/skills/shipper-dot-now/conqueror-skills/conqueror-keyword-clustering"><img src="https://agentmods.dev/badge/skills/shipper-dot-now/conqueror-skills/conqueror-keyword-clustering/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/shipper-dot-now/conqueror-skills/conqueror-keyword-clustering"><img src="https://agentmods.dev/badge/skills/shipper-dot-now/conqueror-skills/conqueror-keyword-clustering.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.00057 | $0.00826 |
| Opus 5 | $0.00028 | $0.00413 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
conqueror-keyword-clustering 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 11d 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.
This is a copy
84% identical to keyword-clustering — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conqueror Keyword Clustering
Goal
Group keywords into page-level clusters and decide which existing or new page should target each cluster. This is a keyword mapping workflow, not just a semantic grouping exercise.
Required inputs
projectId- A keyword list, saved keyword tag, seed topic, or target domain
- Optional existing URLs/pages to map against
If keywords are not provided, use list_saved_keywords for saved sets, research_keywords for seed discovery, or get_ranked_keywords when the user starts from a target domain.
Conqueror MCP tools
list_saved_keywords: fetch an existing keyword set, optionally filtered by tags.research_keywords: expand a seed when the user starts from a topic.get_ranked_keywords: gather exact ranking keywords and URLs when the user starts from a domain or page.get_search_console_performance: when Search Console is connected, pull real queries withdimensions: ["query","page"]to map terms to the pages already earning impressions and to surface cannibalization (one query splitting clicks across multiple URLs).get_serp_results: validate whether keywords belong on the same page by checking SERP overlap and intent.get_local_serp_results: use for local SEO clusters when Maps/local-pack intent should affect page mapping.save_keywords: optionally tag final clusters after user confirmation.
Workflow
- Gather the candidate keyword set.
- Use
get_search_console_performance(dimensions["query","page"]) when Search Console is connected to start from real queries and the pages already ranking for them. - Use
get_ranked_keywordsfor domain/page-driven clustering. - Use
search_local_businessesandget_local_serp_resultswhen proximity, local packs, or Google Business results determine whether terms belong on location pages.
- Use
- Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.
- Build clusters around intent and page type:
- Same SERP intent and similar ranking pages belong together.
- Different intent, buyer stage, or SERP format should be split.
- Similar words do not guarantee the same cluster.
- For important borderline terms, use a small
get_serp_resultsbatch to check overlap. - Assign each cluster to:
- Existing URL, if supplied and appropriate
- New page recommendation, if no existing page fits
- Do-not-target / later bucket, if weak or off-strategy
- Identify cannibalization risk when multiple pages would target the same intent. When Search Console is connected, confirm it from real data with
get_search_console_performance(dimensions: ["query","page"]) — the same query sending impressions to multiple URLs. - Ask before applying cluster tags with
save_keywords.
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.
- 11d ago First seen · 77 lines · 57 tokens per session scan A a49b45076b62
conqueror-keyword-clustering is a skill published in the GitHub repository Shipper-dot-now/conqueror-skills (0 stars, last pushed 21d ago), licensed MIT. It adds 57 tokens to every session and 826 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to keyword-clustering, differing in 17 lines, and is treated as a copy.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…