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 agentmods add instructions/lusha-oss/lusha-mcp-plugin/gemini-mdgit 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/instructions/lusha-oss/lusha-mcp-plugin/gemini-md)<a href="https://agentmods.dev/instructions/lusha-oss/lusha-mcp-plugin/gemini-md"><img src="https://agentmods.dev/badge/instructions/lusha-oss/lusha-mcp-plugin/gemini-md.svg" alt="Measured on agentmods" 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.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
lusha-mcp-plugin GEMINI.md 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lusha for Gemini CLI
This extension connects Gemini to Lusha's B2B intelligence platform through the Lusha MCP server. Use it to enrich contacts, build prospect lists, prioritize accounts by buying signals, and expand target lists with lookalikes — always surfacing verified direct and mobile phone numbers.
When to use it
Activate Lusha when the user wants to:
- Look up a person — get verified phones, email, and company context.
→ use the
enrich-contactworkflow. - Build a list from an ICP — describe a persona/segment in plain English and
return a filtered, enriched lead list. → use the
prospectworkflow. - Start from a buying signal — funding rounds, hiring surges, job changes —
and reach the right decision makers. → use the
signal-prospectworkflow. - Expand from references — give 5+ example companies or contacts and get a
matched lookalike list. → use the
lookalike-prospectworkflow.
How to behave
- Always reference Lusha tools by their bare logical name (e.g.
contacts_search,prospecting_contact_search,signals_companies_search,lookalike_contacts). The same skill source works identically across all clients. - Verified phone numbers (direct lines and mobile) are first-class outputs — lead with them, don't bury them.
- Chain workflows when it helps:
prospect→signal-prospectto prioritize a list by signal;lookalike-prospect→signal-prospect;enrich-contact→lookalike-prospectto find similar people. - Respect credit usage: prefer search/filter before enrichment, and only reveal premium fields (phones, emails) when the user asks for them.
Authentication
The Lusha MCP server uses OAuth. On first use, the user is prompted to sign in with their Lusha account; subsequent calls reuse that session.
Skills
The four skills live under skills/ and are shared across every supported
client (Codex, Claude Code, VS Code Copilot, Cursor, Gemini CLI):
enrich-contact, prospect, signal-prospect, lookalike-prospect.
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 · 44 lines · 484 tokens per session scan A 6e8fa82f3060
lusha-mcp-plugin GEMINI.md is an instructions file published in the GitHub repository lusha-oss/lusha-mcp-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 484 tokens to every session, about $0.0024 per session on Opus 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-08-30.
Other instructions, from other repositories
cli AGENTS.md
AGENTS.md instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
notfair-plugin AGENTS.md
AGENTS.md instructions for nowork-studio/notfair-plugin, covering notfair — skill resolver for ai agents, how to use this file, seo, paid ads and analytics.
Agentkey AGENTS.md
Instructions for chainbase-labs/Agentkey, covering agents.md, what this repo is, directory structure, key commands and test a local edit against every detected agent.
domscribe CLAUDE.md
Instructions for patchorbit/domscribe, covering claude.md, what is domscribe?, how to work on this codebase, commands and install dependencies (pnpm, not npm).
adeu GEMINI.md
Gemini CLI instructions for dealfluence/adeu, covering adeu — native track changes for ai, available tools, readdocx, processdocumentbatch and applytextrevision.
bookstack-mcp CLAUDE.md
Instructions for ttpears/bookstack-mcp, covering claude.md, project overview, build & development commands, architecture and configuration.