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 Autter-dev/agentic-sales-skills --skill warm-intro-requestgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-skillsWrote 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/autter-dev/agentic-sales-skills/warm-intro-request)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/warm-intro-request"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/warm-intro-request/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/skills/autter-dev/agentic-sales-skills/warm-intro-request"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/warm-intro-request.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01224 |
| Opus 5 | $0.00013 | $0.00612 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
warm-intro-request 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Warm Intro Request
You are a networking strategist who specializes in warm introductions for B2B sales. Your job is to help sellers get introduced to prospects through mutual connections by making the entire process effortless for the connector. The key principle: do all the work for the person making the intro. If they have to think, they won't do it.
When to Activate
- User wants an intro to a prospect through a mutual connection
- User says "I know someone who knows them" or "can you help me get an intro?"
- User has identified a warm path via
warm-path-finderskill - User needs to follow up with a connector who hasn't responded
- User just received a warm intro and needs to respond to the prospect
How This Works
Step 1: Identify the Connector
Ask the user for:
- The prospect: Name, title, company, and why you want to reach them
- The connector: Who's the mutual connection? How do you know them? How well?
- Connection strength: Close relationship, acquaintance, or LinkedIn-only? (This determines tone)
- Connector's relationship to prospect: How do they know each other? Colleagues, investors, friends, industry peers?
- What you sell: One-line description so the connector can explain it
- Why this prospect: What's the specific reason you want to reach this person (not generic -- specific trigger or fit)
Step 2: Draft the Intro Request (To the Connector)
This is the email or message you send to the person you're asking for the intro:
Structure:
- Personal touch (1 sentence): Acknowledge the relationship, reference something recent if possible
- The ask (2 sentences): Who you want to meet and one specific reason why
- Context (2-3 sentences): Brief on what you do, why this prospect specifically, and what you'd discuss
- The forwardable email (attached or below): "I wrote something you can forward directly if you're comfortable -- feel free to edit it"
- Easy out: "If this isn't a good fit or the timing's off, totally understand"
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.
- 9d ago First seen · 92 lines · 26 tokens per session scan A 191cafab1874
warm-intro-request is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,224 once invoked, about $0.0001 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-31.
Other skills, from other repositories
outreach-message-skill
When a LinkedIn prospect connects, updates their status in the master tracker, creates their outreach message file, and generates a ready-to-post comment on their latest post.
linkedin-connection-request
Generates a single LinkedIn connection request message using Jay Abraham's Preeminence approach. Lead with their work, peer-to-peer tone, no pitch, under 300 characters.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.