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 cnfeat/top-pm-skills --skill media-relationsgit clone --depth 1 https://github.com/cnfeat/top-pm-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/cnfeat/top-pm-skills/media-relations)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/media-relations"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/media-relations/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/cnfeat/top-pm-skills/media-relations"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/media-relations.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.00039 | $0.00668 |
| Opus 5 | $0.00019 | $0.00334 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
media-relations 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Media Relations
Help the user build effective relationships with journalists and secure press coverage using insights from 2 product leaders.
How to Help
When the user asks for help with media relations:
- Understand their goal - Ask what kind of coverage they're seeking (launch announcement, thought leadership, feature story) and what stage they're at
- Prepare the story - Help them craft a compelling angle that's newsworthy, not just promotional
- Identify the right targets - Guide them on finding the right reporters and publications for their story
- Execute the pitch - Help them write effective pitches and manage the outreach process
Core Principles
Offer exclusives, pitched one at a time
Emilie Gerber: "I stagger it because we're offering exclusives, and I highly recommend offering exclusives." Don't blast your story to every reporter simultaneously. Offer an exclusive to your top target, wait for their response, then move to the next.
Follow the prep-target-pitch framework
Jason Feifer: "Step one is prep... Step two is figuring out who to pitch... Step three is the actual pitch." Preparation means having your story, angles, and assets ready. Targeting means finding reporters who actually cover your space. Pitching means concise, relevant outreach.
Build relationships before you need them
The best media relationships are built over time, not when you need coverage. Engage with journalists' work, provide helpful information even when you don't have news, and become a trusted source.
Think about what's interesting to readers, not you
Reporters care about their readers, not your company. Frame your story around trends, problems, or insights that their audience cares about. Your product is the supporting detail, not the headline.
Questions to Help Users
- "What's the angle that makes this newsworthy beyond just being your announcement?"
- "Who are the specific reporters who cover companies like yours? Have you read their recent work?"
- "Do you have assets ready - images, quotes, data - that make the reporter's job easier?"
- "Are you offering this as an exclusive? Who's your top target outlet?"
- "What's your timeline? Do you have flexibility to work with the reporter's schedule?"
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.
- 11d ago First seen · 58 lines · 39 tokens per session scan A 14ae55dc9954
media-relations is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 668 once invoked, about $0.0002 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…