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 runxhq/runx --skill google-search-consolegit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/google-search-console)<a href="https://agentmods.dev/skills/runxhq/runx/google-search-console"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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/runxhq/runx/google-search-console"><img src="https://agentmods.dev/badge/skills/runxhq/runx/google-search-console.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.01293 |
| Opus 5 | $0.00022 | $0.00647 |
| Sonnet 5 | $0.00009 | $0.00259 |
| Haiku 4.5 | $0.00004 | $0.00129 |
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 6d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Search Console
Use this skill when an operator needs Search Console evidence that another model or workflow can act on: which queries and pages are gaining or losing visibility, whether a URL is indexed, which properties and sitemaps are visible, or whether an exact sitemap should be submitted.
The skill owns the Search Console procedure and evidence shape. It does not own OAuth, credential storage, tenant configuration, or connector routing. A local, self-hosted, third-party, or Runx-hosted connector is equally valid when it implements the declared provider operations and scopes. Connector identifiers, credential handles, provider-config keys, service URLs, and tenant ids belong in the operator's Runx grant and connector configuration, never in this package or its packets.
Operating model
Start with the narrowest question.
- Use
performancefor live query/page/search-performance evidence. - Use
inspect-urlfor the current indexed state of one canonical URL. - Use
sitesorsitemapsto discover accessible resources before assuming a property or sitemap exists. - Use
normalize-performanceonly when Search Console-shaped results were already supplied by a trusted import or connector test. Its packet saysprovider_status: not_called; it is not live-provider proof. - Use
plan-sitemapand thensubmit-sitemapfor an exact, reviewable sitemap mutation. Submission requires a matching scoped grant and provider readback. - Use
plan-indexingto test whether a request belongs in Google's restricted Indexing API lane. Ordinary page-indexing requests are refused.
A useful performance run names the property, date range, search type, data state,
and row bound. It defaults to the page dimension; supply another ordered set only
when the decision needs it. Keep dimensions minimal: adding query, page, country,
device, date, hour, or search appearance changes aggregation and can produce a
much larger, privacy-filtered result. Use hourly_all only with the hour
dimension; those rows are provisional and their timestamps use Google's reported
offset.
What ships with it
8 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.
- 6d ago First seen · 119 lines · 43 tokens per session scan A bf6ab059b5f6
google-search-console is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,293 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-09-03.
Other skills, from other repositories
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.