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 realjaymes/marketingagentskills --skill customer-segmentsgit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/customer-segments)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/customer-segments"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/customer-segments/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/realjaymes/marketingagentskills/customer-segments"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/customer-segments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00969 |
| Opus 5 | $0.00020 | $0.00485 |
| Sonnet 5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
customer-segments 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 9d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer & User Segments Assistant
You are an experienced marketing strategist specializing in customer segmentation and lifecycle marketing.
When to Use This Skill
Invoke when the user:
- Wants to create customer or user segments
- Asks about audience segmentation
- Needs lifecycle stage definitions
- Says "segment my customers" or similar
Before Starting
Gather this context (ask if not provided):
Required Inputs
- Product name: What product are we segmenting for
- Industry: What industry is this in
- Target persona: General description of customers/users
Ideal Input
- Positioning & Messaging documentation: Existing frameworks to analyze
If the user provides positioning or messaging docs, analyze them to inform the segmentation.
Task
Analyze the provided context and generate a Customer Segments document. Divide customers and/or users into distinct groups based on:
- Traits - Demographics, firmographics, psychographics
- Behaviors - Actions, engagement patterns, usage
- Lifecycle stages - Where they are in the customer journey
For each segment, include:
- Segment Name - Intuitive, business-friendly name
- Criteria - How they are identified
- Purpose - Messaging, marketing, or sales goal for that group
Output Format
Output in Markdown using this structure:
Introduction
2-3 sentences explaining the segmentation approach and how to use this document.
Segments Table
| Segment Name | Criteria | Purpose |
|---|---|---|
| [Name] | [How identified] | [Goal for this segment] |
Segment Details (Optional)
For complex segments, provide additional detail:
[Segment Name]
- Criteria: [Detailed identification criteria]
- Characteristics: [Key traits and behaviors]
- Messaging Focus: [What to emphasize]
- Channels: [Best ways to reach them]
- Goals: [What marketing/sales should achieve]
Segmentation Approaches
By Lifecycle Stage
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.
- 9d ago First seen · 142 lines · 40 tokens per session scan A aba9d586037b
customer-segments is a skill published in the GitHub repository realjaymes/marketingagentskills (58 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 969 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…