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/lusha-oss/lusha-mcp-pluginWrote 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/lusha-oss/lusha-mcp-plugin/gemini-extension)<a href="https://agentmods.dev/plugins/lusha-oss/lusha-mcp-plugin/gemini-extension"><img src="https://agentmods.dev/badge/plugins/lusha-oss/lusha-mcp-plugin/gemini-extension/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/lusha-oss/lusha-mcp-plugin/gemini-extension"><img src="https://agentmods.dev/badge/plugins/lusha-oss/lusha-mcp-plugin/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lusha 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": "lusha",
"version": "0.1.3",
"description": "Connect Lusha to Gemini to pull verified B2B data, contact data, and company data — including verified emails, direct dials, mobile numbers, and real-time buying signals — straight into your terminal. Lusha is the B2B data layer behind 300M+ verified contacts, used for sales intelligence, prospecting, data enrichment, and lead enrichment across sales, marketing, and RevOps workflows. Backed by GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance. Perfect for building prospect lists, researching accounts before a call, qualifying inbound leads, and natural language prospecting inside Gemini CLI.\n\nUse Lusha to:\n- Find contacts and decision makers by role, company, industry, or seniority — \"Find 10 VPs of RevOps at Series B SaaS companies in NYC\"\n- Pull verified emails, direct dials, and mobile numbers with 98% email deliverability and 85% phone accuracy — \"Get the verified work email and mobile number for the Head of Marketing at Notion\"\n- Enrich CRM records and inbound leads with firmographics, technographics, headcount, revenue, and buying signals — \"Enrich these 25 webinar signup domains with industry, tech stack, and recent hiring signals\"\n- Track signals across target accounts — funding rounds, leadership hires, hiring surges, and tech stack changes — \"Show me the buying signals from the last 90 days for these 15 accounts\"\n- Find lookalike accounts based on your closed-won customers — \"Find 20 companies that look like these 5 customers\"",
"mcpServers": {
"lusha": {
"httpUrl": "https://mcp.lusha.com/mcp/gemini",
"headers": {
"X-Lusha-Plugin": "gemini",
"X-Lusha-Plugin-Version": "0.1.3"
}
}
}
}
What ships with it
1 file beside gemini-extension.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 First seen · 15 lines scan A e3644e5416f9
lusha is a plugin published in the GitHub repository lusha-oss/lusha-mcp-plugin (4 stars, last pushed 6d 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-10-14.
Other plugins, from other repositories
shopify-plugin
Shopify developer tools for Claude Code — search Shopify docs, generate and validate GraphQL, Liquid, and UI extension code. Skill scripts send usage telemetry (queries, code, model/client identifiers) to shopify.dev by default; set OPTOUTINSTRUMENTATION=true, or create an empty file at /.config/shopify-ai-toolkit/o.
shopify-plugin
shopify-plugin. Agent plugins/extensions for CLIs and IDEs.
looker
Connect to Looker and interact with your data using LookML.
skarn-guard
Real-time guard on five Claude Code pre-execution hook events (tool calls, permission decisions, submitted and expanded prompts, and subagent creation) plus a response-end advisory that flags an action leaking a secret, installing a malicious package, or exfiltrating data, plus the skarn-audit skill (scan sessions and.
skarn-recall
Skill: reconstruct what you worked on from your AI coding sessions (recent, stats, redacted export). Reads session content, so it ships separately from skarn-guard. Backed by the Skarn session engine.
cloud-sql-postgresql
Create, connect, and interact with a Cloud SQL for PostgreSQL database and data.