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 amirjahfar1/Google-Search-Console-GSC-MCP --skill full-seo-auditgit clone --depth 1 https://github.com/amirjahfar1/Google-Search-Console-GSC-MCPWrote 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/amirjahfar1/google-search-console-gsc-mcp/full-seo-audit)<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/full-seo-audit"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/full-seo-audit/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/amirjahfar1/google-search-console-gsc-mcp/full-seo-audit"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/full-seo-audit.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.00058 | $0.00617 |
| Opus 5 | $0.00029 | $0.00309 |
| Sonnet 5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
full-seo-audit 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full SEO Audit
Chains together the individual diagnostic skills and cross-references their findings, instead of running them one at a time in isolation. The value is in step 7 — the same symptom (e.g. a declining page) often gets explained differently depending on which other checks it also shows up in.
Steps
- Call
list_propertiesto confirm the exactsite_url. - Run the
indexing-auditlogic — top 20 pages by impressions, batch-inspected for indexing verdicts. - Run the
sitemap-health-checklogic — sitemap errors/warnings and submitted-vs-indexed gaps. - Run the
cannibalization-checklogic — queries with two or more competing pages. - Run the
content-decay-reportlogic — pages on a 90-day downward trend. - Run the
new-vs-lost-querieslogic — queries that disappeared entirely in the last 28 days. - Cross-reference findings across steps to determine root cause instead of listing symptoms in isolation:
- A page flagged in content-decay (step 5) that also appears in cannibalization (step 4) → the real cause is likely cannibalization, not staleness. Recommend consolidation, not a content refresh.
- A page flagged in content-decay (step 5) that also has a not-indexed/canonical-mismatch verdict (step 2) → the cause is technical, not content quality. Recommend a technical fix first.
- A lost query (step 6) tied to a page with a sitemap indexed-count gap (step 3) → the page may have dropped out of the index entirely. Prioritize resubmission and inspection over content work.
- A page appearing in none of the other checks but still lost clicks → likely external (algorithm update, competitor, or SERP feature change) — note as lowest-confidence, monitor only.
Output format
One consolidated markdown report, sections in priority order:
- Critical — indexing failures and sitemap errors affecting live, high-traffic pages
- High — cannibalization conflicts and lost queries with significant impressions
- Medium — content decay not explained by a technical or cannibalization cause
- Low — minor sitemap warnings, low-impression issues
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 · 37 lines · 58 tokens per session scan A 2170ca70971b
full-seo-audit is a skill published in the GitHub repository amirjahfar1/Google-Search-Console-GSC-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 617 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-09-01.
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…
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.
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…
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…