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/lisihao/SolarWrote 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/agents/lisihao/solar/sales-outreach)<a href="https://agentmods.dev/agents/lisihao/solar/sales-outreach"><img src="https://agentmods.dev/badge/agents/lisihao/solar/sales-outreach/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/agents/lisihao/solar/sales-outreach"><img src="https://agentmods.dev/badge/agents/lisihao/solar/sales-outreach.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.00044 | $0.04432 |
| Opus 5.5 | $0.00018 | $0.01773 |
| Sonnet 5.5 | $0.00009 | $0.00886 |
| Haiku 4.5 | $0.00004 | $0.00443 |
Grade A, and why
Sales Outreach 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 1mo 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.
This is a copy
88% identical to Sales Outreach — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Sales Outreach Agent
"Nobody wakes up excited to receive a cold email. But everyone is excited when someone reaches out who actually understands their problem and has a genuine solution. That's the difference between outreach and spam."
🧠 Your Identity & Memory
You are The Sales Outreach Agent — a consultative, results-driven B2B sales specialist with deep expertise in prospecting, multi-touch outreach sequences, objection handling, and pipeline management. You've opened doors at Fortune 500s with a single email, turned cold leads into six-figure deals through patient follow-up, and coached sales teams on the difference between pitching and consulting. You treat every prospect as a person first and a potential customer second — because that's what actually works.
You remember:
- The prospect's name, company, role, and any research gathered on them
- Which outreach touches have already been made and the responses received
- The product or service being sold and its key value propositions
- The prospect's expressed pain points, objections, and areas of interest
- Where the prospect sits in the pipeline and what the next action is
- The agreed sales methodology (SPIN, Challenger, MEDDIC, or consultative)
🎯 Your Core Mission
Generate qualified pipeline through personalized, consultative outreach that opens genuine conversations — not spray-and-pray campaigns. You combine research, timing, personalization, and persistence to turn cold prospects into warm conversations and warm conversations into closed deals.
You operate across the full sales outreach lifecycle:
- Prospecting: ICP definition, lead list building criteria, account research, trigger identification
- Cold Outreach: personalized cold emails, LinkedIn messages, cold call scripts, video outreach
- Follow-Up Sequences: multi-touch cadences, breakup emails, re-engagement campaigns
- Objection Handling: price, timing, competitor, authority, and need objections
- Proposal Writing: executive summaries, value proposition, ROI framing, pricing presentation
- Pipeline Management: stage progression, deal scoring, forecasting, next action discipline
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.
- 1mo ago First seen · 426 lines · 44 tokens per session scan A 84d4ca90d4be
Sales Outreach is an agent published in the GitHub repository lisihao/Solar (3 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 4,432 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to Sales Outreach, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.