customer-support

customer-support is a skill for Claude Code from djbelieny/nova. It costs 62 tokens per session (1,762 once invoked), scanned A, original, MIT.

A set of guidance for handling customer support work, from writing replies to organizing tickets and support information.

In plain words
What is it for?
Use it to answer complaints and questions, calm frustrated customers, create FAQs and templates, prioritize tickets, and analyze common support problems.
Why use it?
It helps turn difficult or repetitive customer interactions into clear, consistent responses and workflows.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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.

agentmods
npx agentmods add skills/djbelieny/nova/customer-support
Any agent
npx skills add djbelieny/nova --skill customer-support
Clone the repo
git clone --depth 1 https://github.com/djbelieny/nova

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/djbelieny/nova/customer-support.svg)](https://agentmods.dev/skills/djbelieny/nova/customer-support)
Your own site
<a href="https://agentmods.dev/skills/djbelieny/nova/customer-support"><img src="https://agentmods.dev/badge/skills/djbelieny/nova/customer-support.svg" alt="Measured on agentmods" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00062 $0.01762
Opus 5 $0.00031 $0.00881
Sonnet 5 $0.00012 $0.00352
Haiku 4.5 $0.00006 $0.00176

Measured 5d ago against content hash 7509571c3145, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

customer-support 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 5d 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.

.claude/skills/customer-support/SKILL.md · 241 lines

How it starts

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

Customer Support

This skill handles customer support operations — from drafting individual responses to building complete support systems and playbooks.

When to Use This Skill

  • Drafting responses to customer complaints, questions, or feedback
  • De-escalating angry or frustrated customers
  • Creating FAQ pages and knowledge bases
  • Building support response templates
  • Triaging and prioritizing support tickets
  • Analyzing support trends and common issues
  • Writing apology emails or service recovery messages
  • Creating onboarding guides for customers
  • Setting up support workflows and escalation paths
  • Training support team members

Response Framework

The HEARD Method (for all support interactions)

  1. Hear — Acknowledge what they said specifically (not generic "we understand")
  2. Empathize — Show you get why it's frustrating/concerning
  3. Apologize — Take ownership (even if it's not your fault)
  4. Resolve — State the specific action you're taking
  5. Delight — Add something unexpected (discount, priority, extra help)

Tone Guidelines

Always:

  • Use the customer's name
  • Write like a human, not a bot
  • Be specific about next steps and timelines
  • Own the problem ("I'll fix this" not "this will be looked into")
  • Match their urgency level

Never:

  • Use corporate jargon ("per our policy", "at this time")
  • Blame the customer ("you should have...")
  • Make promises you can't keep
  • Use passive voice for accountability ("a mistake was made")
  • Copy-paste generic responses without personalization

Response Templates by Situation

Complaint / Something Went Wrong
Hey [Name],

I completely understand your frustration with [specific issue] — that's not the experience we want for you.

I've [specific action taken: issued a refund / escalated to team / fixed the issue], and you should see [result] within [timeframe].

To make up for the trouble, [delight: here's a discount / I've upgraded your account / I've added X to your account].

If anything else comes up, reply here and I'll handle it personally.

[Your name]

Read the full file on GitHub · 241 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. 5d ago First seen · 241 lines · 62 tokens per session scan A 7509571c3145

Subscribe to this mod's changes

customer-support is a skill published in the GitHub repository djbelieny/nova (5 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,762 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

commonly

You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…

Team-Commonly/commonly · 0 tokens

officecli-commonly-templates

Use this skill when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Trigger on: 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final…

Team-Commonly/commonly · 182 tokens

github

Interact with GitHub (issues, PRs, repos, releases) using the gh CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.

Team-Commonly/commonly · 49 tokens

markdown-converter

Convert binary documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, images) to clean LLM-friendly Markdown using Microsoft's markitdown Python tool. Use when a user attaches a binary file and you need to read its contents.

Team-Commonly/commonly · 57 tokens

pandic-office

Convert Markdown to PDF (or DOCX/EPUB/HTML) using the pandoc CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file.

Team-Commonly/commonly · 59 tokens

pdf

Manipulate PDF files — extract text, count pages, render thumbnails, merge or split documents. Use for PDF-specific operations that don't fit markdown-converter (general read) or pandic-office (write from markdown).

Team-Commonly/commonly · 49 tokens