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 surendranb/google-search-console-mcp --skill search-appearance-auditgit clone --depth 1 https://github.com/surendranb/google-search-console-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/surendranb/google-search-console-mcp/search-appearance-audit)<a href="https://agentmods.dev/skills/surendranb/google-search-console-mcp/search-appearance-audit"><img src="https://agentmods.dev/badge/skills/surendranb/google-search-console-mcp/search-appearance-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/surendranb/google-search-console-mcp/search-appearance-audit"><img src="https://agentmods.dev/badge/skills/surendranb/google-search-console-mcp/search-appearance-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.00019 | $0.00206 |
| Opus 5.5 | $0.00008 | $0.00082 |
| Sonnet 5.5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
search-appearance-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 yesterday.
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.
What it actually says
Search Appearance Audit
When to use: The GSC API restricts grouping by searchAppearance alongside other dimensions (like query). Use this pattern to perform a server-side join and find which queries trigger featured snippets, AI overviews, or rich results.
How to execute:
- Call
get_search_analyticswithdimensions=["searchAppearance"],row_limit=50to find what special appearances your site triggers overall. - Call
get_search_analyticswithdimensions=["query"],row_limit=1000to get your query performance. - Client-side heuristic join: Look for queries where Position <= 1.5 but CTR is < 1.5%. This is the "Silent Reference" pattern indicating your content is powering a featured snippet or AI overview but the user is satisfied on the SERP without clicking.
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.
- yesterday First seen · 14 lines · 19 tokens per session scan A 080c4940a0c6
search-appearance-audit is a skill published in the GitHub repository surendranb/google-search-console-mcp (40 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 206 once invoked, about $0.0001 per session on Opus 5.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-10-29.
Other skills, from other repositories
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
coding-agents-hooks-authoring
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
hitl
Rosetta CRITICAL MUST skill to load as Prep Step 3 Step 2 — immediately after orchestrator-contract, right before loading any workflow. Loads the session-wide approval-gate protocol governing when to stop and wait vs proceed. WITHOUT IT decisions proceed silently, violating enterprise policy. Activate it for ALL tasks…