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 conquer-keywordgit 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/conquer-keyword)<a href="https://agentmods.dev/skills/shipper-dot-now/conqueror-skills/conquer-keyword"><img src="https://agentmods.dev/badge/skills/shipper-dot-now/conqueror-skills/conquer-keyword/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/conquer-keyword"><img src="https://agentmods.dev/badge/skills/shipper-dot-now/conqueror-skills/conquer-keyword.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.00064 | $0.00748 |
| Opus 5 | $0.00032 | $0.00374 |
| Sonnet 5 | $0.00013 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
conquer-keyword 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 9d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conquer a Keyword
Goal
Take one target keyword and improve the connected WordPress site's best-matching page for it — better title, excerpt, structure, and content, matched to search intent — then propose the rewrite for human review. Proposing changes nothing on the site: the user reviews a diff in Conqueror and decides whether to apply it to the original post.
Required inputs
projectId- The target keyword
- Optionally, a specific post/page to improve. Otherwise pick the best match.
If projectId is missing, use list_projects first. If the project has no WordPress connection, stop and tell the user to connect one in the project's settings page (Site URL + application password).
Conqueror MCP tools
list_wordpress_posts: find candidate posts (search by keyword). Includes drafts.get_wordpress_post: read the current title, excerpt, and body of the target post. The body is raw editor content — it may contain Gutenberg block comments (<!-- wp:… -->) and shortcodes.get_serp_results: see what currently ranks for the keyword.get_keyword_metrics: optional — attach volume/difficulty/intent to the keyword when useful context.propose_wordpress_revision: store the rewrite for review. Pass the post'spostId; the current version is snapshotted so the user gets a diff and can roll back after applying.
You cannot apply, publish, or roll back a change. Those are the user's clicks in Conqueror.
Workflow
- Find the target page.
list_wordpress_postswith the keyword as search. If one post is clearly the best match, use it; otherwise show the top candidates and ask the user to pick. Read it withget_wordpress_post. - Understand the competition.
get_serp_resultsfor the keyword; read 2-3 top-ranking pages to see the depth, structure, and subtopics that win. Note the dominant search intent (informational, commercial, transactional). - Rewrite for the keyword.
- Title: include the keyword naturally, match intent, stay compelling.
- Excerpt: a meta-description-quality summary (~150 chars) with the keyword.
- Content: clear heading hierarchy (keyword in the lead), cover the gaps competitors expose, keep the site's voice, preserve real links and images. Improve what exists — do not pad with fluff or invent facts, prices, or statistics.
- Preserve any block comments and shortcodes that were in the original, or the post loses its structure when the change is applied.
- Show before/after. A compact comparison of title, excerpt, and structure plus the key content changes, with a one-line rationale per change.
- Propose it.
propose_wordpress_revisionwith the post'spostId. Give the user the returned review link, and say plainly that nothing on the live site has changed yet.
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.
- 9d ago First seen · 47 lines · 64 tokens per session scan A 6516b39b0931
conquer-keyword is a skill published in the GitHub repository Shipper-dot-now/conqueror-skills (0 stars, last pushed 18d ago), licensed MIT. It adds 64 tokens to every session and 748 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-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…
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…