beachhead-segment

beachhead-segment is a skill for Claude Code from VandanaAjayDubey111/great-pm. It costs 58 tokens per session (3,154 once invoked), scanned A, original, MIT.

A market-segment selection guide for finding the first group of customers to target. A beachhead segment is a small, promising starting market for a product.

In plain words
What is it for?
Use it to compare target customer groups, choose an initial market, and plan an entry strategy.
Why use it?
It helps avoid trying to sell to everyone at once and compares which customer group has the strongest need and best chance of adoption.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Codex.

Part of the great-pm plugin — 114 skills, 34 commands, 48 agents, 5 hooks shipped together

Good fit Use it to compare target customer groups, choose an initial market, and plan an entry strategy.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vandanaajaydubey111/great-pm/beachhead-segment
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 VandanaAjayDubey111/great-pm --skill beachhead-segment
Clone the repo
git clone --depth 1 https://github.com/VandanaAjayDubey111/great-pm

Made for: Claude Code.

Or install great-pm, the plugin that ships this one along with the rest of its 114 skills, 34 commands, 48 agents, 5 hooks.

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 beachhead-segment

README.md
[![agentmods](https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/beachhead-segment/github.svg)](https://agentmods.dev/skills/vandanaajaydubey111/great-pm/beachhead-segment)
Your own site
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/beachhead-segment"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/beachhead-segment/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 beachhead-segment

Your own site · 80×15
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/beachhead-segment"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/beachhead-segment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,154 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 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.00058 $0.03154
Opus 5.5 $0.00023 $0.01262
Sonnet 5.5 $0.00012 $0.00631
Haiku 4.5 $0.00006 $0.00315

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

Security

Grade A, and why

beachhead-segment 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/great-pm/skills/beachhead-segment/SKILL.md · 209 lines

How it starts

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

Codex host binding

  • Treat references to Claude slash workflows as the equivalently named Codex skill.
  • Before delegating to any specialist, read the great-pm-runtime skill and the selected packaged role file.
  • Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex spawn_agent call with that role and a bounded assignment.
  • For the spawn tool's task_name or agent_name identifier, replace canonical role-name hyphens with underscores (query-refiner-pm → query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
  • Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
  • If spawn_agent is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
  • Resolve bundled paths from the installed GreatPM plugin root.
  • Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
  • Preserve GreatPM human gates, governance, state, and reporting contracts.

Provenance. Vendored from phuryn/pm-skills@beachhead-segment (MIT, Paweł Huryn / Product Compass — github.com/phuryn/pm-skills). Adapted into great-pm 2026-05-29 with attribution. Host agent: gtm-strategist.

Beachhead Segment

Overview

Identify the first beachhead market segment for product launch. This skill evaluates potential market segments against key criteria to find your initial winning segment that enables fast PMF validation and adjacent expansion.

When to Use

  • Choosing a first market for your product
  • Targeting an initial customer segment
  • Planning initial market entry strategy
  • Deciding where to focus limited resources
  • Validating GTM assumptions with early adopters

Key Evaluation Criteria

1. Burning Pain Point

Does this segment experience an acute, unmet problem?

  • Daily frustration with the status quo
  • Significant productivity loss or cost impact
  • Emotional urgency to find a solution
  • Current workarounds are expensive or fragile
  • Problem is getting worse over time

Read the full file on GitHub · 209 lines

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 First seen · 209 lines · 58 tokens per session scan A f04f26b091c6

Subscribe to this mod's changes

beachhead-segment is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 3,154 once invoked, about $0.0002 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-21.