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 T4wroot/agentic-seo --skill google-search-consolegit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/google-search-console)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/google-search-console"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/google-search-console/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/t4wroot/agentic-seo/google-search-console"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/google-search-console.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.00137 | $0.03212 |
| Opus 5.5 | $0.00055 | $0.01285 |
| Sonnet 5.5 | $0.00027 | $0.00642 |
| Haiku 4.5 | $0.00014 | $0.00321 |
Grade A, and why
google-search-console 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 1mo 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.
This is a copy
100% identical to google-search-console — 277 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics: Google Search Console
Guides analysis of Google Search Console (GSC) data: performance metrics, indexing, sitemaps, Core Web Vitals, and rich results. Covers best practices for monthly monitoring and actionable insights.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope
- Performance: Clicks, impressions, CTR, average position; API for export
- Insights: Simplified overview; top/trending content and queries
- Indexing: Pages indexed, pages not indexed, reasons (Coverage)
- Technical: Sitemaps, Core Web Vitals, Enhancements
- API: searchanalytics.query for programmatic access
- Methodology: How to read charts, avoid common mistakes, correlate with releases
Analysis Best Practices
Chart Reading
| Practice | Why |
|---|---|
| Focus one metric at a time | Stacked bar charts hide fluctuations; toggle off other metrics to see each clearly |
| Don't compare just two points | End-of-month vs prior month misses mid-month drama; examine full trend |
| Check beyond top 10 | Many reports default to top 10; scroll or paginate for more rows |
| Screenshot charts | GSC retains limited history; save images for future reference |
| Record in spreadsheet | Export at month-end; use formulas to track correlations over time |
| Track release dates | Join dev standups, read release notes; correlate GSC shifts with deployments |
Investigation Workflow
- Pinpoint date: When did the metric change?
- Correlate: Any releases, CMS changes, server maintenance, third-party code?
- Decide: Investigate, correct, overlook, or monitor closely
- Loop in: Product or dev team for root cause
Key Reports & Metrics
1. Performance (Search Results)
Location: Performance ? Search results
| Metric | Use |
|---|---|
| Clicks | Traffic from Google Search |
| Impressions | How often site appeared in results |
| CTR | Whether users think page answers query |
| Average position | Ranking trend |
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.
- 1mo ago First seen · 279 lines · 137 tokens per session scan A 0649408558f2
google-search-console is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 3,212 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to google-search-console, differing in 277 lines, and is treated as a copy.
Other skills, from other repositories
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
backlink-outreach
Find, evaluate, pitch and track natural backlink and content partnerships. Prospects come from the GEO citation data rather than a generic blog search: the targets are the pages an AI already cites when answering your category questions. Research runs on the Monid tool layer (web search and scrape, authority metrics…
content-thicken
Evidence-driven blog driver. Takes ONE target from the fused search plus AI-answer content library, pulls the real questions it has to answer, drafts a thick long-form guide against a template contract, validates it deterministically, and stops at preview. Two modes, thicken an already-earning post IN PLACE (never…
geo-monitor
Run and read the GEO pipeline, which measures whether AI answer engines mention, recommend and cite your site. Puts a fixed registry of real user questions to an answer engine through the Monid tool layer, detects the three signals plus competitors, and turns "a rival is named and we are not" into a tracked work…
seo-intake
Run and read the SEO intake pipeline. Pulls the organic keyword set for your domain and for each competitor through the Monid tool layer, computes the gap locally, and routes every keyword to the one action that can help it (write-new / striking / build-depth / defend / noise). Use when asked to refresh the SEO queue…
optimise-seo
Use when explicitly authorized to implement a bounded, approved SEO action in a codebase or content system, verify the exact change, and report its limitations; do not use for broad audits, self-approved production changes, or outcome guarantees.