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 eddiebelaval/squire --skill customer-support-replygit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/customer-support-reply)<a href="https://agentmods.dev/skills/eddiebelaval/squire/customer-support-reply"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/customer-support-reply/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/eddiebelaval/squire/customer-support-reply"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/customer-support-reply.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 25 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00015 | $0.04987 |
| Opus 5 | $0.00008 | $0.02493 |
| Sonnet 5 | $0.00003 | $0.00997 |
| Haiku 4.5 | $0.00002 | $0.00499 |
Grade A, and why
Customer Support Reply 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 7d 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 — 710 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Support Reply
The Customer Support Reply skill helps you craft empathetic, effective responses to customer inquiries, issues, and complaints. Whether you're resolving a technical problem, handling a frustrated customer, providing product guidance, or managing a difficult situation, this skill ensures your responses are professional, helpful, and customer-focused.
This skill understands that support responses can make or break customer relationships. They need to balance empathy with efficiency, acknowledge frustration while providing solutions, and maintain professionalism while being genuinely helpful. The skill helps you handle everything from simple questions to complex escalations.
Great support responses solve problems, build trust, and create positive customer experiences even in difficult situations. This skill makes creating them efficient while maintaining the quality and care that drives customer satisfaction and loyalty.
Core Workflows
Workflow 1: Standard Support Response
- Understand Issue: Read customer message carefully
- Acknowledge Concern: Show empathy and understanding
- Provide Solution: Give clear, actionable answer
- Verify Understanding: Ensure solution is clear
- Offer Follow-Up: Make yourself available for next steps
Workflow 2: Escalation Response
- Assess Severity: Understand scope and impact
- Empathize Deeply: Acknowledge their frustration
- Take Ownership: Show accountability
- Provide Timeline: Set clear expectations
- Escalate Internally: Loop in appropriate teams
- Follow Through: Update customer on progress
Workflow 3: Template Creation
- Identify Pattern: Recognize recurring issues
- Create Base Response: Build reusable template
- Mark Personalization Points: Identify where to customize
- Add Variables: Include merge fields for common data
- Test and Refine: Use in real scenarios and improve
Quick Reference
| Action | Command/Trigger |
|---|---|
| Technical issue | "Reply to customer with technical issue [description]" |
| Billing question | "Respond to billing inquiry about [issue]" |
| Feature request | "Reply to feature request for [feature]" |
| Complaint | "Respond to complaint about [problem]" |
| Refund request | "Handle refund request due to [reason]" |
| Bug report | "Acknowledge bug report for [issue]" |
| Account issue | "Resolve account access problem" |
| How-to question | "Explain how to [do something]" |
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.
- 7d ago First seen · 710 lines · 15 tokens per session scan A 2dfbfa46080c
Customer Support Reply is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 25d ago), licensed MIT. It adds 15 tokens to every session and 4,987 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
Customer Support Reply
Craft empathetic, effective customer support responses that solve problems.
Escalation Handler
Handle escalated support issues with structured triage, communication, and resolution processes.
routine-from-chat
Turn a plain-language "do this automatically" request into a routine — either event-triggered ("text me when I get an email from my landlord") or scheduled ("remind me every Friday at 9am"). For third-party events (Gmail, GitHub, Slack…) it confirms with the guardian and then subscribes to the connector trigger so the…
novu-design-workflow
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…
human-cli
Reach the actual human you're working for via the human CLI (ask/approve/choose/tell) when you need a decision, approval, or notification and no one is watching this terminal right now. Use for background/autonomous/scheduled runs, risky or irreversible actions, and genuine multi-way ambiguity — not for routine…
novu-manage-preferences
Configure notification preferences in Novu at the workflow and subscriber level. Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides. Use when setting up notification opt-in/opt-out, configuring per-channel…