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.
/plugin marketplace add Bin-Huang/google-search-console-clinpx agentmods add plugins/bin-huang/google-search-console-cli/marketplacegit clone --depth 1 https://github.com/Bin-Huang/google-search-console-cliGrade A, and why
google-search-console-cli marketplace 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 3d 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.
What it actually says
{
"name": "google-search-console-cli",
"owner": {
"name": "Benn Huang"
},
"metadata": {
"description": "Google Search Console CLI & Skills for AI agents, built on the official Search Console and Webmasters APIs",
"version": "0.1.0"
},
"plugins": [
{
"name": "google-search-console-cli",
"description": "Google Search Console analysis and site management skill for AI agents",
"source": "./",
"skills": [
"./skills/google-search-console-cli"
]
}
]
}
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.
- 3d ago First seen · 21 lines scan A aa656d0aa3e4
google-search-console-cli marketplace is a plugin published in the GitHub repository Bin-Huang/google-search-console-cli (20 stars, last pushed 4mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
mcp-search-console
Connect Google Search Console to Claude Code. Query SEO data, inspect URLs, audit indexing, and identify content opportunities through natural language.
ga4
GA4 reports, traffic sources, landing pages, events, funnels, annotations and realtime. Read-only; run ga4oauthstart after install to authorise.
gsc
Search Analytics, URL Inspection and sitemaps from Google Search Console. Read-only; run gscoauthstart after install to authorise.
metrika
Traffic sources, landing pages, search phrases, goals, geo and devices from the Yandex.Metrica Stat API. Read-only; run metrikaoauthstart after install.
aparser
Bridge to your own self-hosted A-Parser: SERP, suggests and 150+ parsers via its HTTP API. Read-only; needs your own A-Parser licence and server.
seo-tools
All eight servers at once: XMLStock, XMLRiver, Wordstat, Search Console, Analytics 4, Yandex.Webmaster, Yandex.Metrica and the A-Parser bridge. 100 tools — prefer the single-server plugins unless you need the lot.