customer-context

customer-context is a skill for Claude Code from stefanoskarakasis/Product-Marketing-Skills. It costs 189 tokens per session (3,339 once invoked), scanned A, original, MIT.

A dated brief about one existing customer, assembled from connected sales and support sources such as a CRM, email, calls, documents, chat, and usage data. A CRM is a system for tracking customer relationships and sales activity.

In plain words
What is it for?
It prepares someone for a customer call, renewal, escalation, or handover by summarizing ownership, contacts, opportunities, conversations, support, usage, and evidenced concerns.
Why use it?
It gives a seller or customer manager one current view instead of requiring them to search many tools. It also highlights missing information, risks, relevant competitors and objections, and changes since the previous brief.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the pmm-sales plugin — 3 skills, 3 commands shipped together

Good fit It prepares someone for a customer call, renewal, escalation, or handover by summarizing ownership, contacts, opportunities, conversations, support, usage, and evidenced concerns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stefanoskarakasis/product-marketing-skills/customer-context
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 stefanoskarakasis/Product-Marketing-Skills --skill customer-context
Clone the repo
git clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-Skills

Made for: Claude Code.

Or install pmm-sales, the plugin that ships this one along with the rest of its 3 skills, 3 commands.

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 customer-context

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/customer-context"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/customer-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 189 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,339 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.00189 $0.03339
Opus 5.5 $0.00076 $0.01336
Sonnet 5.5 $0.00038 $0.00668
Haiku 4.5 $0.00019 $0.00334

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

Security

Grade A, and why

customer-context 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 today.

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.

pmm-sales/skills/customer-context/SKILL.md · 161 lines

How it starts

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

Customer Context

A seller or CSM walks into a customer call with five tabs open and none of them says what matters. This skill reads the tools you connect, puts the current state of one customer first, flags what is missing or at risk, and shows only what changed since the last brief. Because it reads your brain, it also says whether the customer fits your ICP, which competitors and objections are in play, and which claims you may repeat. What it learns across many customers goes back to the PMM as proposals, never as silent writes.

Trigger

  • When: Someone needs the current state of one named customer before a call, a renewal, an escalation or a handover, or asks about it in a Slack thread.
  • Not for: A prospect or a company you do not sell to yet; say so, then offer to build the brief from pasted notes. A competitor → competitive-profile. A competitor inside a live deal → competitive-battlecard. Who decides and who blocks in a deal → stakeholder-maps or buyer-personas. A customer story or reference → customer-stories. A pipeline or forecast across many customers → N/A in this plugin.
  • Example prompts:
    • "@Claude catch me up on Northwind" (Slack thread)
    • "Customer context for Northwind before Thursday's renewal call."
    • "What changed at Northwind since last month?" (delta only)
    • "Is Northwind at risk?" (ask, usually from Slack)
    • "Customer context for Acme" (edge: Acme is a prospect; stops and says so)
    • "Customer context for Northwind" with no CRM connected (edge: works from pasted notes and says what is missing)

Inputs

  • Args: A customer name or domain, optionally a mode: brief (default), since (delta only) or ask (one question, thread-sized). A one-line question about a named customer is an ask.
  • Defaults: Lookbacks follow the sales cycle in brain Section 7, else email 90 days, chat 60, CRM activity 90, calls 90. The surface decides shape and delivery (references/surfaces.md): a Slack thread gets a short reply, other surfaces a full brief.
  • Context keys: the brain (/foundation/brain.md, gaps.md, me.md for format only); /context/customers/ (earlier briefs, _patterns.md); /context/competitor-profiles/ and /context/battlecards/ (read only); the ~~ connectors in references/connectors.md.
    • Brain contract: Reads Section 2 (anti_persona, committee_roles, size, industry), Section 3 (alternatives, objections, switching_forces), Section 6 (approved proof, forbidden_claims), Section 8 (prohibited, approvals). Never writes the brain. Anything it learns is a proposal for product-marketing-context and other skills (references/feed-forward.md).

Read the full file on GitHub · 161 lines

Files

What ships with it

7 files 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. today Changed · +5 tokens per session f47f1ade4b8d
  2. 4d ago First seen · 161 lines · 184 tokens per session scan A 008d4626cfc2

Subscribe to this mod's changes

customer-context is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (9 stars, last pushed yesterday), licensed MIT. It adds 189 tokens to every session and 3,339 once invoked, about $0.0008 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-11-04.

Related

customer-context compared with skills from other repositories

customer-context next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
customer-contextstefanoskarakasis/Product-Marketing-SkillsSkill9yesterdayMITA189Claude Code
reportsmk-labs/claude-pluginsSkill111mo agoMITA57Claude Code
k8s-rightsizesmk-labs/claude-pluginsSkill111mo agoMITA62Claude Code
owasp-securitysmk-labs/claude-pluginsSkill111mo agoMITA72Claude Code
figsmk-labs/claude-pluginsSkill111mo agoMITA45Claude Code
brandsmk-labs/claude-pluginsSkill111mo agoMITA64Claude Code
workspace-rulessmk-labs/claude-pluginsSkill111mo agoMITA83Claude Code