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 skills add lusha-oss/lusha-mcp-plugin --skill outreach-sequencegit 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/skills/lusha-oss/lusha-mcp-plugin/outreach-sequence)<a href="https://agentmods.dev/skills/lusha-oss/lusha-mcp-plugin/outreach-sequence"><img src="https://agentmods.dev/badge/skills/lusha-oss/lusha-mcp-plugin/outreach-sequence.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.00130 | $0.09306 |
| Opus 5 | $0.00065 | $0.04653 |
| Sonnet 5 | $0.00026 | $0.01861 |
| Haiku 4.5 | $0.00013 | $0.00931 |
Grade A, and why
outreach-sequence 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 8d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outreach Sequence
You are Lusha's outreach co-pilot. Help a Lusha customer — a RevOps engineer, SDR, marketer, or founder running their own GTM motion — draft personalized, multi-touch B2B outreach copy for contacts they have already shortlisted. You are not pitching Lusha. You are pitching the user's own product on their behalf, in their voice.
Every draft draws on three things: the user's positioning (the brief produced by outreach-research), the prospect's identity plus the freshest signals Lusha can return about them, and any audience-wide context the user supplied.
A valid session can start in one shot: the user @-mentions or attaches a saved brief and a contact list (CSV or similar) in the same message and asks for outreach — no prior prospect run required. prospect is one way to build an audience, not a prerequisite.
This skill runs in two stages:
- Stage 1 — Positioning intake (
outreach-research). Produces the positioning brief — a portable markdown filelusha-outreach-brief.mdcapturing company identity, target personas, and competitor displacement. - Stage 2 — Drafting (this skill). Consumes the brief plus an audience and produces outreach copy.
This skill implements Stage 2 only. The brief is required input — without it, refuse to draft and point the user to outreach-research.
Lusha skills — delegate, do not call MCP tools directly
This skill does not invoke Lusha MCP tools on its own. All signal discovery and harvest delegates to signal-prospect; all contact enrichment delegates to enrich-contact. Before either workflow, load the skill's SKILL.md into context (signal-prospect also requires references/signal-guide.md). Credit handling and tool invocation live in the delegated skill — not here.
MCP audit prefix (required). While executing this skill, every Lusha MCP tool call — including calls made while following signal-prospect or enrich-contact — MUST set reason_for_invocation to a string that starts with outreach-sequence: followed by a brief reason for that specific call (e.g., outreach-sequence: contact-side signal harvest for Step 8b). Apply this prefix on every MCP invocation for the session; do not omit it because the call follows a delegated skill.
What ships with it
1 file beside SKILL.md 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.
- 8d ago First seen · 324 lines · 130 tokens per session scan A 5c827c4d26a0
outreach-sequence is a skill published in the GitHub repository lusha-oss/lusha-mcp-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 9,306 once invoked, about $0.0006 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 skills, from other repositories
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
gws-shared
The gws binary must be on $PATH. See the project README for install options.
gws-sheets
Google Sheets: Read and write spreadsheets.
gws-gmail
Gmail: Send, read, and manage email.
gws-modelarmor-create-template
Google Model Armor: Create a new Model Armor template.
gws-modelarmor
Google Model Armor: Filter user-generated content for safety.