Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add imisic/claude-marketplace/plugin install search-visibilityWrote 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/imisic/claude-marketplace/a-seo-gsc)<a href="https://agentmods.dev/skills/imisic/claude-marketplace/a-seo-gsc"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/a-seo-gsc/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/imisic/claude-marketplace/a-seo-gsc"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/a-seo-gsc.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.00029 | $0.03233 |
| Opus 5 | $0.00015 | $0.01617 |
| Sonnet 5 | $0.00006 | $0.00647 |
| Haiku 4.5 | $0.00003 | $0.00323 |
Grade A, and why
a-seo-gsc 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 8d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
a-seo-gsc: Search Console → action plan
Google Search Console already knows what is wrong with a site's search performance. This skill fetches its Performance data over the API or ingests manual exports, runs a deterministic parser, applies a full analysis playbook (adapting to the site type), and writes a prioritized action plan you can actually execute. It works on any website, not one specific project.
The output is a doc: docs/seo/YYYY-MM-DD-action-plan.md in the target project (or wherever the user keeps analyses), plus a spoken summary of the headline finding and the top moves.
First run: what to give me, and where to get it
Open by asking which route they are on, because both are fully supported and the answer changes only the first step:
Do you have the Search Console API set up for this property, or would you rather download the reports by hand? Both work. The API saves clicking and returns one extra thing the download cannot, but hand-exported CSVs are a first-class input here, not a fallback.
Route A: they have the API, or want it
python3 "${CLAUDE_PLUGIN_ROOT}/skills/a-seo-gsc/scripts/fetch_gsc.py" \
--property sc-domain:example.com --days 90
That writes current/ and previous/ directories of CSVs in Google's own export shape. If the property has no service-account key yet, do not hand them a link. Run Setup mode below.
Then ask for the two reports no API serves:
Two exports I cannot fetch, both from Indexing → Pages:
- Click Export on the summary. That gives the indexed vs not-indexed counts and the reason breakdown.
- Click the biggest "not indexed" reason (usually "Crawled - currently not indexed"), then Export the URL table. Repeat for any other large reason. This is the one people skip and the most useful file in the set. Drop the zips in a folder next to the fetched data. Optional extras: the Links report (top linking sites, also no API), Sitemaps, and Core Web Vitals.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago Changed · +60 lines · +9 tokens per session 2fc53996cef7
- 12d ago First seen · 81 lines · 20 tokens per session scan A 55345adc3708
a-seo-gsc is a skill published in the GitHub repository imisic/claude-marketplace (2 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 3,233 once invoked, about $0.0001 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
read-only-gh-pr-review
Review backend pull requests for correctness, security, performance, maintainability, and test coverage using GitHub CLI plus local repository inspection. Use when asked to review service-layer/API/database changes, audit backend branch diffs, summarize backend risk, or produce actionable must-fix/should-fix feedback.
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
meta-reviewing-api-reviewing
Backend code review patterns. Use when reviewing API routes, database operations, auth middleware, and server utilities. Covers injection, boundary validation, authorization coverage, secret/PII exposure, error leakage, and query patterns.
mold
Turn a high-leverage design decision into an approved spec through grounded dialogue. Use it when a leverage trigger fires (auth, irreversible effects, concurrency, contracts, destructive ops, a new slice, a cross-slice dependency, an invariant gap) or when the user asks for a spec or design. Typical phrases include…
patterns
This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", "add configuration", or builds features involving database operations, REST/GraphQL APIs, pub/sub patterns, or service configuration. Provides implementation patterns that…
architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".