public-relations

public-relations is a skill for Claude Code from cbrock84/headcount. It costs 65 tokens per session (813 once invoked), scanned A, original, MIT.

A public-relations guide for finding newsworthy stories, contacting journalists, making announcements, handling interviews, and responding to damaging coverage.

In plain words
What is it for?
Use it to plan press work, write pitches or releases, identify journalists, prepare interview responses, judge newsworthiness, and manage crises.
Why use it?
It helps separate genuine news from ordinary company updates and gives outreach a clearer story, audience, and reason to matter now.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the marketing plugin — 19 skills shipped together

Good fit Use it to plan press work, write pitches or releases, identify journalists, prepare interview responses, judge newsworthiness, and manage crises.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cbrock84/headcount/public-relations
About the project

headcount is an organization of independently installable Claude Code plugins, each grouping skills for a department such as finance, security, or demand generation. Claude Code users install the departments they need and invoke their skills for specialized work; the catalogue entries are skills and related agent tooling from that organization.

cbrock84/headcount · 2,077 stars · on GitHub · cbrock84.github.io

Install

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.

Any agent
npx skills add cbrock84/headcount --skill public-relations
Clone the repo
git clone --depth 1 https://github.com/cbrock84/headcount

Made for: Claude Code.

Or install marketing, the plugin that ships this one along with the rest of its 19 skills.

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 public-relations

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

agentmods 80×15 button for public-relations

Your own site · 80×15
<a href="https://agentmods.dev/skills/cbrock84/headcount/public-relations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/public-relations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 813 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00065 $0.00813
Opus 5.5 $0.00026 $0.00325
Sonnet 5.5 $0.00013 $0.00163
Haiku 4.5 $0.00006 $0.00081

Measured 1mo ago against content hash 914ecc56660d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/marketing/skills/public-relations/SKILL.md · 75 lines

How it starts

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

Public relations

Newsworthy is a high bar

Most company news is not news. Before pitching, find the actual story — the thing a journalist's readers would care about with your company removed from the sentence.

Genuinely newsworthy: a first, a significant number, a counter-intuitive finding from data you uniquely have, a named conflict, a consequential person moving. Not newsworthy: a funding round of ordinary size, a feature release, a partnership, an award, a rebrand.

If there is no story, the answer is to build one — original research is the most reliable way — not to pitch harder.

Pitching

Journalists receive hundreds of pitches a day and reject most in seconds.

  • Pitch a person, not an outlet. Read three of their recent pieces first and reference one specifically and accurately. Generic personalization is worse than none.
  • Subject line is the pitch. If it does not carry the story, nothing else will be read.
  • Three sentences: the story, why now, why you can speak to it. Offer the assets — data, interview, images — rather than attaching them.
  • No embargo without agreement. Declaring one unilaterally is not binding and reads as presumptuous.
  • One follow-up, then stop.

Interviews

Decide the two or three things you want to have said, and find honest routes back to them. Never speculate, never say anything you would not want printed, and treat nothing as off the record unless explicitly agreed in advance — and even then, assume it may not hold.

"I don't know, I'll find out" is a complete and respectable answer.

When a story goes badly

  • Speed matters, but accuracy matters more. A fast wrong statement extends the story.
  • Say what happened, what you are doing, and when you will update. Only that.
  • Never dispute a factual detail you have not verified, and never attack the reporter. Both guarantee a second story.
  • Correct genuine errors privately, with evidence, and specifically. Vague complaints about tone achieve nothing.

Read the full file on GitHub · 75 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. 1mo ago Changed · +7 lines 914ecc56660d
  2. 1mo ago First seen · 68 lines · 65 tokens per session scan A c72e43a68bc0

Subscribe to this mod's changes

public-relations is a skill published in the GitHub repository cbrock84/headcount (2,077 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 813 once invoked, about $0.0003 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

launch-google-search

Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.

markifact/markifact-mcp · 56 tokens

negative-keyword-sweep

Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.

markifact/markifact-mcp · 56 tokens

rotate-creative

Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.

markifact/markifact-mcp · 57 tokens

go

Compatibility entry for Visual Stack's former /vstack:go command. Runs the wireframe and UI review tool, now called review. Use only when the user invokes /vstack:go.

Cavalry-Collective/visual-stack · 41 tokens

save

Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.

XTSoftwareLabs/neatcontext-plugins · 49 tokens

dns

This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…

proyecto26/system-design-skills · 131 tokens