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 earned-media-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/earned-media-outreach)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/earned-media-outreach"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/earned-media-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/earned-media-outreach"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/earned-media-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.00061 | $0.01834 |
| Opus 5 | $0.00030 | $0.00917 |
| Sonnet 5 | $0.00012 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00183 |
Grade A, and why
earned-media-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:
- earned-media-outreach — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Earned Media Outreach
When to Use
- Founder wants to get featured on podcasts as a guest
- Founder wants press coverage from journalists and tech publications
- Founder wants to build relationships with media for ongoing exposure
- Founder wants to identify which podcasts and publications reach their target audience
- Founder wants to write pitch emails that actually get responses
Context Required
- Founder's story and what makes it interesting (not just what the product does)
- Target audience — who are you trying to reach through media? (customers, investors, talent)
- Topics the founder can speak on with genuine authority
- Previous media experience (if any)
- Upcoming newsworthy events (launch, funding round, milestone, contrarian take)
Workflow
- Define the media angle — journalists and podcast hosts don't cover products, they cover stories. Identify your angles:
- Founder story: unusual background, pivot story, "I quit X to build Y"
- Trend story: "Why [trend] is changing [industry]" — you as the expert source
- Data story: original data or insights from your product/market
- Contrarian take: challenge conventional wisdom in your space
- Milestone: funding round, user milestone, revenue milestone, major partnership
- Build the target list — research podcasts and publications that reach your audience:
- Podcasts: search Apple Podcasts, Spotify, ListenNotes, and Podchaser by topic. Look for shows that have had similar-stage founders as guests. Check episode frequency (active shows only) and audience size (download numbers if available).
- Publications: identify journalists who cover your space. Read their last 10 articles. Follow them on X/Twitter. Check if they have a tips inbox or preferred pitch method.
- Newsletters: Substack writers, industry newsletter authors who feature startups
- YouTube channels: tech reviewers, industry commentators
- Tier the list — prioritize by reach x relevance:
- Tier 1 (5-10): perfect audience fit, worth significant prep time
- Tier 2 (10-20): good fit, standard outreach
- Tier 3 (20+): adjacent audience, batch outreach
- Write the pitches — different formats for different targets:
- Podcast pitch: short, personal, focused on what you'll teach their audience (not what you'll promote)
- Journalist pitch: newsworthy angle, relevant data, why their readers care, not a press release
- Newsletter pitch: how featuring you provides value to their subscribers
- Send and follow up — outreach cadence:
- Initial pitch
- Follow-up 1 (5-7 days later, add new context)
- Follow-up 2 (7-10 days later, final touch — offer a different angle)
- Move on after 3 touches with no response
- Prepare for appearances — for confirmed bookings:
- Research the host's style and past episodes
- Prepare 3-5 talking points with stories (not bullet points)
- Have a clear CTA for listeners (one thing, not five)
- Send the host a prep sheet with your bio, headshot, topics, and any questions to avoid
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 · 152 lines · 61 tokens per session scan A 320a131b3991
earned-media-outreach is a skill published in the GitHub repository shawnpang/startup-founder-skills (321 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 1,834 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…