claude_everything: Skill for Claude Code

.agents/skills/investor-outreach/SKILL.md

investor-outreach is a skill for Claude Code, Codex from burgebj/claude_everything. It costs 54 tokens per session (553 once invoked), scanned A, a copy of investor-outreach, MIT.

A writing guide for investor communications during fundraising. It covers cold emails, introductions, follow-ups, investor updates, and messages tailored to a specific investor or fund.

In plain words
What is it for?
Use it to contact angel investors, venture capital firms, strategic investors, or accelerators and to follow up after meetings or unanswered messages.
Why use it?
Generic fundraising messages are easy to ignore and often make unclear requests. This add-on helps turn company information into short, specific messages with a clear next step.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is burgebj/claude_everything's own configuration. It tells Claude Code and Codex how to work on claude_everything itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude_everything configures →

Part of the everything-claude-code plugin — 37 skills, 5 commands, 16 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to burgebj/claude_everything. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/burgebj/claude_everything/ecc-tools/everything-claude-code-1775042279843/.agents/skills/investor-outreach/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/burgebj/claude_everything

Made for: Claude Code, Codex.

Or install everything-claude-code, the plugin that ships this one along with the rest of its 37 skills, 5 commands, 16 agents.

Wrote 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.

agentmods badge for investor-outreach

README.md
[![agentmods](https://agentmods.dev/badge/skills/burgebj/claude_everything/investor-outreach/github.svg)](https://agentmods.dev/skills/burgebj/claude_everything/investor-outreach)
Your own site
<a href="https://agentmods.dev/skills/burgebj/claude_everything/investor-outreach"><img src="https://agentmods.dev/badge/skills/burgebj/claude_everything/investor-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.

agentmods 80×15 button for investor-outreach

Your own site · 80×15
<a href="https://agentmods.dev/skills/burgebj/claude_everything/investor-outreach"><img src="https://agentmods.dev/badge/skills/burgebj/claude_everything/investor-outreach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00553
Opus 5 $0.00027 $0.00277
Sonnet 5 $0.00011 $0.00111
Haiku 4.5 $0.00005 $0.00055

Measured 12d ago against content hash 247034b0b404, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

investor-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 12d 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.

Origin

This is a copy

83% identical to investor-outreach — 7 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.

.agents/skills/investor-outreach/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Investor Outreach

Write investor communication that is short, concrete, and easy to act on.

When to Activate

  • writing a cold email to an investor
  • drafting a warm intro request
  • sending follow-ups after a meeting or no response
  • writing investor updates during a process
  • tailoring outreach based on fund thesis or partner fit

Core Rules

  1. Personalize every outbound message.
  2. Keep the ask low-friction.
  3. Use proof instead of adjectives.
  4. Stay concise.
  5. Never send copy that could go to any investor.

Hard Bans

Delete and rewrite any of these:

  • "I'd love to connect"
  • "excited to share"
  • generic thesis praise without a real tie-in
  • vague founder adjectives
  • "no fluff"
  • begging language
  • soft closing questions when a direct ask is clearer

Cold Email Structure

  1. subject line: short and specific
  2. opener: why this investor specifically
  3. pitch: what the company does, why now, and what proof matters
  4. ask: one concrete next step
  5. sign-off: name, role, and one credibility anchor if needed

Personalization Sources

Reference one or more of:

  • relevant portfolio companies
  • a public thesis, talk, post, or article
  • a mutual connection
  • a clear market or product fit with the investor's focus

If that context is missing, state that the draft still needs personalization instead of pretending it is finished.

Follow-Up Cadence

Default:

  • day 0: initial outbound
  • day 4 or 5: short follow-up with one new data point
  • day 10 to 12: final follow-up with a clean close

Do not keep nudging after that unless the user wants a longer sequence.

Warm Intro Requests

Make life easy for the connector:

  • explain why the intro is a fit
  • include a forwardable blurb
  • keep the forwardable blurb under 100 words

Post-Meeting Updates

Include:

  • the specific thing discussed
  • the answer or update promised
  • one new proof point if available
  • the next step

Quality Gate

Before delivering:

  • the message is genuinely personalized
  • the ask is explicit
  • the proof point is concrete
  • filler praise and softener language are gone
  • word count stays tight

Read the full file on GitHub · 88 lines

Files

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.

Changes

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.

  1. 12d ago First seen · 88 lines · 54 tokens per session scan A 247034b0b404

Subscribe to this mod's changes

investor-outreach is a skill published in the GitHub repository burgebj/claude_everything (7 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 553 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to investor-outreach, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

sector-rotation

An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.

HKUDS/Vibe-Trading · 39 tokens

strategy-pivot-designer

Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.

tradermonty/claude-trading-skills · 28 tokens

twitter-reader

Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…

himself65/finance-skills · 161 tokens

chenhao-limit-up

A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.

questflowai/investorskills · 44 tokens

furusato

A Japanese hometown-tax donation manager for furusato nozei, a system where donations to municipalities can qualify for an income-tax or local-tax deduction. It reads donation receipts, stores donation records, and calculates deduction limits.

kazukinagata/shinkoku · 102 tokens

reading-receipt

An image-reading workflow for extracting structured information from receipts, invoices, and hometown-tax donation certificates. It can first extract text from PDFs and otherwise read their images.

kazukinagata/shinkoku · 64 tokens