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 shawnpang/startup-founder-skills --skill partnership-outreachgit clone --depth 1 https://github.com/shawnpang/startup-founder-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/shawnpang/startup-founder-skills/partnership-outreach)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/partnership-outreach"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/partnership-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/skills/shawnpang/startup-founder-skills/partnership-outreach"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/partnership-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.00051 | $0.02252 |
| Opus 5 | $0.00026 | $0.01126 |
| Sonnet 5 | $0.00010 | $0.00450 |
| Haiku 4.5 | $0.00005 | $0.00225 |
Grade A, and why
partnership-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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- partnership-outreach — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Partnership Outreach
When to Use
Activate when a founder needs to identify and reach out to potential partners, write partnership emails, propose integrations, or create co-marketing proposals. Also use when the user says "I want to partner with X," "help me write a BD email," "how do I propose an integration," "co-marketing opportunity," or "I need a channel partner strategy."
Context Required
From startup-context or the user:
- Your product and positioning — What you do and who you serve
- Partnership goal — Integration, co-marketing, reseller/channel, referral, or strategic alliance
- Target partner — Company name, relevant product/team, why they are a good fit
- Shared audience — The overlapping customer segment you both serve
- Your leverage — What you bring to the table (users, distribution, technology, content, brand)
- Current traction — Metrics that demonstrate your value as a partner (users, revenue, growth rate)
Workflow
- Gather context — Read startup-context if available. Understand the product, traction, and partnership goals.
- Identify partner fit — Use the Partner Evaluation Framework to assess whether this is a strong partnership opportunity.
- Map the win-win — Define what each side gets from the partnership. If you cannot articulate both sides, the proposal will fail.
- Find the right contact — Identify the BD, partnerships, or product person at the target company. Avoid generic inboxes.
- Draft the outreach — Write the partnership email or LinkedIn message using the frameworks below.
- Prepare the proposal — If the initial outreach gets a response, draft a lightweight partnership proposal (1-2 pages).
- Define success metrics — Propose how both sides will measure whether the partnership is working.
Output Format
Deliver the appropriate materials based on the partnership stage:
- Partner evaluation — Fit assessment using the evaluation framework
- Initial outreach email/message — The first touch to the target partner
- Follow-up sequence — 2-3 follow-ups with different angles
- Partnership proposal — 1-2 page document outlining the partnership structure, mutual benefits, and next steps
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.
- 13d ago First seen · 149 lines · 51 tokens per session scan A b88062284756
partnership-outreach is a skill published in the GitHub repository shawnpang/startup-founder-skills (321 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 2,252 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…