agentmods.dev

customer-context

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

A command for building a current brief about one existing customer from connected business tools. It can show the account's owner, renewal, opportunities, contacts, conversations, support, usage themes, risks, and changes since an earlier brief.

In plain words
What is it for?
It answers questions about a named customer, such as what changed, whether the account is at risk, or how to prepare for an upcoming renewal, and saves the brief for later use.
Why use it?
It saves time spent gathering customer information across systems and gives a focused answer before a call, renewal, escalation, or handover. In Slack, it can reply in the relevant thread.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

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

not rated 9repo +1 yesterday A scan 23 tokens original MIT

Good fit It answers questions about a named customer, such as what changed, whether the account is at risk, or how to prepare for an upcoming renewal, and saves the brief for later use.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/stefanoskarakasis/product-marketing-skills/customer-context
View source ↗ stefanoskarakasis/Product-Marketing-Skills stefanoskarakasis.substack.com
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.

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/commands/stefanoskarakasis/product-marketing-skills/customer-context/github.svg)](https://agentmods.dev/commands/stefanoskarakasis/product-marketing-skills/customer-context)
Your own site
<a href="https://agentmods.dev/commands/stefanoskarakasis/product-marketing-skills/customer-context"><img src="https://agentmods.dev/badge/commands/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/commands/stefanoskarakasis/product-marketing-skills/customer-context"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/customer-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 382 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.00023 $0.00382
Opus 5.5 $0.00009 $0.00153
Sonnet 5.5 $0.00005 $0.00076
Haiku 4.5 $0.00002 $0.00038

Measured 4d ago against content hash 269002988856, 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 4d 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.

pmm-sales/commands/customer-context.md · 36 lines

What it actually says

/pmm-sales:customer-context -- Customer Context

Builds the current state of one existing customer: owner, renewal, open opportunities, contacts and who has really replied, the latest calls and threads, support and usage themes, and up to five evidenced flags. Checks the customer against your brain (ICP fit, competitors, objections, claims you may use) and, when an earlier brief exists, shows only what changed. In Slack it answers in a short thread reply. Saves the brief to /context/customers/.

Invocation

/pmm-sales:customer-context Northwind
/pmm-sales:customer-context Northwind before Thursday's renewal call
/pmm-sales:customer-context What changed at Northwind since last month?
/pmm-sales:customer-context Is Northwind at risk?

In Slack, tag Claude in a thread: "@Claude catch me up on Northwind".

Workflow

Uses the customer-context skill. Picks the surface (Slack, chat, Cowork, Claude Code or a scheduled run), loads the brain and the last brief, reads the CRM, email, calls, docs, chat, support and usage you have connected, checks the customer against the brain, flags what is missing or at risk, writes the brief in the shape that fits where you are reading, runs a 12-check gate on its own work, saves the record, proposes what other skills should learn once two customers agree, and logs the session. Read-only for your brain, CRM and inbox.

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. 4d ago First seen · 36 lines · 23 tokens per session scan A 269002988856

Subscribe to this mod's changes

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

Claude CodeProject managementclaude-code-marketplaceclaude-code-pluginsclaude-skillsproduct-marketingskill-md
Related

customer-context compared with commands from other repositories

customer-context next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
customer-contextstefanoskarakasis/Product-Marketing-SkillsCommand9yesterdayMITA23Claude Code
getpixsmk-labs/claude-pluginsCommand111mo agoMITA16Claude Code
photo-passsmk-labs/claude-pluginsCommand111mo agoMITA0Claude Code
strategyphuryn/pm-skillsCommand28k9d agoMITA18Claude Code
plan-okrsphuryn/pm-skillsCommand28k9d agoMITA17Claude Code
privacy-policyphuryn/pm-skillsCommand28k9d agoMITA15Claude Code
conjurejohn-farina/claude-pluginsCommand118d agoMITB62Claude Code