account-based-marketing

account-based-marketing is a skill for Claude Code from cbrock84/headcount. It costs 98 tokens per session (997 once invoked), scanned A, original, MIT.

A marketing approach that chooses specific business accounts first, then coordinates marketing and sales efforts around the people involved in buying from each account.

In plain words
What is it for?
It is for selecting target accounts, mapping their buying groups, assigning different effort levels, coordinating campaigns, and measuring account-level results.
Why use it?
It avoids spending broad marketing effort on poorly matched prospects and reduces duplicated or disconnected outreach to the same company.

Skill for Claude Code

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

Part of the demand-generation plugin — 12 skills shipped together

Good fit It is for selecting target accounts, mapping their buying groups, assigning different effort levels, coordinating campaigns, and measuring account-level results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cbrock84/headcount/account-based-marketing
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,093 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 account-based-marketing
Clone the repo
git clone --depth 1 https://github.com/cbrock84/headcount

Made for: Claude Code.

Or install demand-generation, the plugin that ships this one along with the rest of its 12 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 account-based-marketing

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/cbrock84/headcount/account-based-marketing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/account-based-marketing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 997 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 79
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00098 $0.00997
Opus 5.5 $0.00039 $0.00399
Sonnet 5.5 $0.00020 $0.00199
Haiku 4.5 $0.00010 $0.00100

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

Security

Grade A, and why

account-based-marketing 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/demand-generation/skills/account-based-marketing/SKILL.md · 90 lines

How it starts

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

Account-based marketing

Account-based marketing inverts the usual model: instead of generating leads and finding out which accounts they came from, you choose the accounts and work them. It is a good fit for a narrow set of businesses and an expensive mistake for the rest.

Qualify the model before adopting it

It works when deal sizes are large enough to justify per-account effort, the addressable market is small enough to enumerate, buying groups have several people, and sales cycles are long enough for sustained effort to compound.

It does not work when the deal size cannot carry the cost, when the market is too large to name, or when marketing and sales will not actually coordinate. That last one is the usual failure: the tooling gets bought, the account list gets built, and the program becomes a more expensive way to run the same campaigns.

Run the arithmetic first. Total program cost divided by the number of accounts, against expected deal value and a realistic win rate, tells you the tier structure you can afford — or that you cannot afford this at all.

Build the list from fit and evidence, then hold it still

Start from the accounts that already look like your best customers — not by revenue but by why they bought and whether they stayed. Add observable signals: hiring, technology in use, funding, regulatory pressure, a change in leadership.

Then commit. A list that churns quarterly cannot compound, and compounding is the only reason this model beats broad demand generation. Agree the list with sales and get their explicit acceptance, because a list sales does not believe in is a list sales will not work.

Map the buying group, not the contact

Purchases at this size are made by several people with different concerns: the person with the problem, the person with the budget, the person who will operate it, and whoever can veto on security, legal or procurement grounds.

Reaching one champion and mistaking that for account coverage is the most common structural error. Track how many roles you have reached within each account, and treat single-threading as a status that needs fixing rather than a warning to note.

Read the full file on GitHub · 90 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 d6d11e201c04
  2. 1mo ago First seen · 83 lines · 98 tokens per session scan A e148fc6565ca

Subscribe to this mod's changes

account-based-marketing is a skill published in the GitHub repository cbrock84/headcount (2,093 stars, last pushed 9d ago), licensed MIT. It adds 98 tokens to every session and 997 once invoked, about $0.0004 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

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

distributed-search

This skill should be used when the user designs a "search system", needs "full-text search", asks about an "inverted index", "Elasticsearch / OpenSearch", "relevance ranking" (TF-IDF/BM25), "search autocomplete / typeahead", an "indexing pipeline", or "faceted search". It gives the crawl/index/search architecture…

proyecto26/system-design-skills · 117 tokens

sharded-counters

This skill should be used when the user needs a "sharded counter", "distributed counter", to "count likes / views at scale", handles a "high-write counter" or "hot counter contention", asks about "approximate counting", "real-time counts", or "HyperLogLog". It gives the recipe for absorbing write-heavy counting…

proyecto26/system-design-skills · 106 tokens

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