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.
git clone --depth 1 https://github.com/imisic/claude-marketplaceWrote 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/plugins/imisic/claude-marketplace/search-visibility)<a href="https://agentmods.dev/plugins/imisic/claude-marketplace/search-visibility"><img src="https://agentmods.dev/badge/plugins/imisic/claude-marketplace/search-visibility/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/plugins/imisic/claude-marketplace/search-visibility"><img src="https://agentmods.dev/badge/plugins/imisic/claude-marketplace/search-visibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
search-visibility 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 5d 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": "search-visibility",
"displayName": "Search Visibility: SEO and AI Search",
"description": "For website owners and marketers: turn Google Search Console data into a ranked list of SEO fixes, and check whether AI assistants can find, read and cite your site.",
"version": "1.5.0",
"author": {
"name": "Ivan Misic",
"url": "https://ivanmisic.net"
},
"homepage": "https://ivanmisic.net/toolshed/plugins/search-visibility",
"repository": "https://github.com/imisic/claude-marketplace",
"license": "MIT",
"keywords": [
"seo",
"search-console",
"ai-search",
"seo-audit",
"indexing",
"structured-data",
"organic-traffic",
"content-strategy",
"analytics"
],
"documentationUrl": "https://github.com/imisic/claude-marketplace/tree/main/plugins/search-visibility#readme",
"privacyPolicyUrl": "https://github.com/imisic/claude-marketplace/tree/main/plugins/search-visibility#privacy",
"supportUrl": "https://github.com/imisic/claude-marketplace/issues",
"termsOfServiceUrl": "https://github.com/imisic/claude-marketplace/blob/main/LICENSE",
"userConfig": {
"gsc_key_file": {
"type": "file",
"title": "Search Console key file",
"description": "Path to the Google service-account JSON key that the Search Console fetcher uses. Leave it empty if you export reports by hand instead."
}
}
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 184 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 5d ago Changed · +7 lines c46c529d3fa1
- 1mo ago Changed 8dda9287133c
- 1mo ago Changed · +9 lines 1cd16037b044
- 2mo ago Changed 998aff447d24
- 2mo ago First seen · 20 lines scan A d1b1975ea31b
search-visibility is a plugin published in the GitHub repository imisic/claude-marketplace (1 stars, last pushed 5d ago), licensed MIT. 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-31.
search-visibility compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| search-visibilityimisic/claude-marketplace | Plugin | 1 | 5d ago | MIT | A | — | Claude Code |
| fakoli-crewfakoli/fakoli-plugins | Plugin | 4 | 2d ago | MIT | A | — | Claude Code |
| fakoli-plugin-criticfakoli/fakoli-plugins | Plugin | 4 | 2d ago | MIT | A | — | Claude Code |
| rust-network-modulefakoli/fakoli-plugins | Plugin | 4 | 2d ago | MIT | A | — | Claude Code |
| comprehensive-reviewHermeticOrmus/claude-code-game-development | Plugin | 79 | 1mo ago | MIT | A | — | Claude Code |
| backend-api-securityHermeticOrmus/claude-code-game-development | Plugin | 79 | 1mo ago | MIT | A | — | Claude Code |
| backend-architecturejohnkozaris/jko-claude-plugins | Plugin | 11 | 9d ago | MIT | A | — | Claude Code |