agentmods.dev

content-opportunities

content-opportunities is a skill for Claude Code from amirjahfar1/Google-Search-Console-GSC-MCP. It costs 33 tokens per session (381 once invoked), scanned A, a copy of content-opportunities, MIT.

A Search Console report that finds pages or search terms with many appearances but few clicks, ranking just outside the first page. It targets positions 11–20, which are on the second page of results.

In plain words
What is it for?
Use it to find title and description improvements, pages that may need merging, and opportunities to add internal links to raise rankings.
Why use it?
These pages already appear in searches but may lose clicks because of their ranking or search-result wording. They can be prioritized for focused improvements.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the google-search-console-gsc-mcp plugin — 12 skills, 1 MCP server shipped together

not rated 0repo 2mo ago A scan 33 tokens copy · 89% MIT

Good fit Use it to find title and description improvements, pages that may need merging, and opportunities to add internal links to raise rankings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities
View source ↗ amirjahfar1/Google-Search-Console-GSC-MCP
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 amirjahfar1/Google-Search-Console-GSC-MCP --skill content-opportunities
Clone the repo
git clone --depth 1 https://github.com/amirjahfar1/Google-Search-Console-GSC-MCP

Made for: Claude Code.

Or install google-search-console-gsc-mcp, the plugin that ships this one along with the rest of its 12 skills, 1 MCP server.

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 content-opportunities

README.md
[![agentmods](https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities/github.svg)](https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities)
Your own site
<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities/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 content-opportunities

Your own site · 80×15
<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/content-opportunities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 381 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 89% copy Near-identical to another mod 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.00033 $0.00381
Opus 5 $0.00016 $0.00191
Sonnet 5 $0.00007 $0.00076
Haiku 4.5 $0.00003 $0.00038

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

Security

Grade A, and why

content-opportunities 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.

Origin

This is a copy

89% identical to content-opportunities — 4 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.

skills/content-opportunities/SKILL.md · 41 lines

What it actually says

Content Opportunities

Surface quick-win content optimization targets: pages or queries sitting in positions 11–20 with high impression volume but low CTR.

Steps

  1. Call list_properties to confirm the exact site_url.
  2. Call get_advanced_search_analytics with:
    • dimensions=query,page
    • sort_by=impressions
    • sort_direction=descending
    • row_limit=1000
    • start_date = 28 days ago, end_date = today
  3. Filter the results to keep only rows where:
    • position is between 11 and 20 (page 2, just below the fold)
    • impressions > 100 (meaningful search volume)
    • ctr < 0.03 (3% — below average for these positions)
  4. Sort the filtered set by impressions descending.
  5. Return the top 20 rows.

Output format

Present as a table: Query | Page | Position | Impressions | CTR | Opportunity Score

Opportunity Score = impressions × (0.05 − ctr) — a rough estimate of clicks gained if CTR reaches 5%.

Follow the table with specific recommendations for each entry:

  • Title/meta description optimization ideas
  • Whether to merge with a better-ranking page
  • Whether to add internal links to boost the page

Run branded-vs-nonbranded first if the site has a strong brand — it filters out branded queries so the opportunities surfaced here are genuine non-brand growth potential, not brand searches that already convert well.

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 · 41 lines · 33 tokens per session scan A e81feef7420f

Subscribe to this mod's changes

content-opportunities is a skill published in the GitHub repository amirjahfar1/Google-Search-Console-GSC-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 381 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to content-opportunities, differing in 4 lines, and is treated as a copy.

Analytics and metricsMarketing and SEO
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens