title-meta-rewriter

title-meta-rewriter is a skill for Claude Code, Codex from marketingskills/seo. It costs 35 tokens per session (278 once invoked), scanned A, original, MIT.

An SEO writing aid that uses Google Search Console query data to suggest alternative page titles and meta descriptions. It matches wording to what people search for and what they intend to find.

In plain words
What is it for?
Use it to rewrite titles and meta descriptions, compare them with competing search-result wording, and choose options aimed at improving organic click-through rate.
Why use it?
It helps when a page appears in search results but attracts too few clicks. The suggestions use real query evidence instead of relying only on guesswork.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it to rewrite titles and meta descriptions, compare them with competing search-result wording, and choose options aimed at improving organic click-through rate.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marketingskills/seo/title-meta-rewriter
Install

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.

Any agent
npx skills add marketingskills/seo --skill title-meta-rewriter
Clone the repo
git clone --depth 1 https://github.com/marketingskills/seo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for title-meta-rewriter

README.md
[![agentmods](https://agentmods.dev/badge/skills/marketingskills/seo/title-meta-rewriter/github.svg)](https://agentmods.dev/skills/marketingskills/seo/title-meta-rewriter)
Your own site
<a href="https://agentmods.dev/skills/marketingskills/seo/title-meta-rewriter"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/title-meta-rewriter/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.

agentmods 80×15 button for title-meta-rewriter

Your own site · 80×15
<a href="https://agentmods.dev/skills/marketingskills/seo/title-meta-rewriter"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/title-meta-rewriter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00278
Opus 5 $0.00017 $0.00139
Sonnet 5 $0.00007 $0.00056
Haiku 4.5 $0.00003 $0.00028

Measured 11d ago against content hash df0e4f379384, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

title-meta-rewriter 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.

skills/title-meta-rewriter/SKILL.md · 35 lines

What it actually says

Title Meta Rewriter

Overview

Given a page URL and its GSC query performance, produce title and meta description alternatives that better match search intent and improve organic CTR. Uses actual query data to understand what users are searching for.

Inputs

  • Page URL
  • GSC query data for the page (queries driving impressions, CTR per query)
  • Optional: current SERP titles from top-ranking competitors

Workflow

  1. Analyze GSC queries that drive impressions to the page.
  2. Identify the primary query and secondary queries.
  3. Check the current SERP for competitor title patterns.
  4. Evaluate the current title and meta description: does it match the dominant query intent?
  5. Generate 3-5 title alternatives that:
    • Include the primary query or close variant
    • Match the search intent (informational, commercial, etc.)
    • Differentiate from competitor titles
    • Stay within length limits (60 chars for title, 160 for meta)
  6. Generate 2-3 meta description alternatives.
  7. For each alternative, note the expected CTR impact.

Output

Title and meta description alternatives with CTR rationale and recommendation.

Changes

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.

  1. 11d ago First seen · 35 lines · 35 tokens per session scan A df0e4f379384

Subscribe to this mod's changes

title-meta-rewriter is a skill published in the GitHub repository marketingskills/seo (3 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 278 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.

Related

Other skills, from other repositories

os-what-could-go-wrong

ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision…

kharmanskyi/open-steps · 149 tokens

os-check-work

ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against…

kharmanskyi/open-steps · 118 tokens

os-done-or-not

ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from…

kharmanskyi/open-steps · 127 tokens

os-step-by-step

ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do"…

kharmanskyi/open-steps · 180 tokens

os-whats-next

ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is…

kharmanskyi/open-steps · 155 tokens

os-ask-simple

ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - or ask if something is worth doing or if something simpler would do, in any language. Rewrites the question in plain…

kharmanskyi/open-steps · 122 tokens