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 4d 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",
"description": "Two halves of getting found: a-seo-gsc pulls your Google Search Console data over the API (or reads a manual export) and turns it into a prioritized action plan backed by your own numbers, and a-geo-optimizer checks whether AI assistants can fetch, parse, and cite a site, then recommends the technical and content fixes. One diagnoses from data, the other covers the newer search surface.",
"version": "1.3.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",
"geo",
"search-console",
"analytics",
"content-strategy"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 185 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago Changed 998aff447d24
- 8d ago First seen · 20 lines scan A d1b1975ea31b
search-visibility is a plugin published in the GitHub repository imisic/claude-marketplace (2 stars, last pushed 7d 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.
Other plugins, from other repositories
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
pr-sweep
Cross-repo PR sweep: triage all open PRs, run code reviews, merge what's ready, fix quick CI blockers, and report.
review
Code review for a branch, PR, or path — structured output with severity labels and cross-file analysis.
fakoli-plugin-critic
Five specialist critic agents for Claude Code plugin development — agent-critic (frontmatter/color/tools), skill-critic (lazy-loading/no-fuzzy-detection), hook-critic (contract-aware/${CLAUDEPLUGINROOT}), mcp-critic (schema/actor-validation), structure-critic (manifest/CHANGELOG/version-sync). Audit any plugin (your.
devils-advocate
Claude's harshest critic. Evidence required. Perfection impossible.
chorus
Workflow patterns: LLM council, parallel review, parallel debug, second opinion.