customer-experience

customer-experience is a plugin for Claude Code from cbrock84/headcount. Its manifest loads nothing; the 7 skills it bundles cost 569 tokens per session together, scanned A, original, MIT.

A customer-experience plugin for work after a sale is completed. It groups tools for support operations, handling escalations, collecting customer feedback, and helping customers find answers themselves.

In plain words
What is it for?
Use it to organize customer-support processes, manage serious customer issues, run feedback loops, and build self-service help resources.
Why use it?
It gives post-sale customer work a shared home instead of leaving support, success, and feedback disconnected. That makes recurring customer problems easier to track and send back to the product team.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest.

Good fit Use it to organize customer-support processes, manage serious customer issues, run feedback loops, and build self-service help resources.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add cbrock84/headcount
/plugin install customer-experience
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,063 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.

Clone the repo
git clone --depth 1 https://github.com/cbrock84/headcount

Made for: Claude Code.

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-experience

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

Your own site · 80×15
<a href="https://agentmods.dev/plugins/cbrock84/headcount/customer-experience"><img src="https://agentmods.dev/badge/plugins/cbrock84/headcount/customer-experience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 7 skills cost 569 tokens a session between them.
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.
Security

Grade A, and why

customer-experience 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/customer-experience/.claude-plugin/plugin.json · 17 lines

What it actually says

{
  "name": "customer-experience",
  "description": "Support operations, escalation management, voice of customer, and self-service. Owns what the customer experiences after the sale.",
  "version": "1.0.0",
  "author": {
    "name": "Chris Brock"
  },
  "repository": "https://github.com/cbrock84/headcount",
  "keywords": [
    "support",
    "customer-success",
    "escalation",
    "voice-of-customer",
    "service"
  ]
}
Contents

What it installs

The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 569 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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 · 17 lines scan A 42314ebc346e

Subscribe to this mod's changes

customer-experience is a plugin published in the GitHub repository cbrock84/headcount (2,063 stars, last pushed 29d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.