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 personamanagmentlayer/pcl --skill customer-support-expertgit clone --depth 1 https://github.com/personamanagmentlayer/pclWrote 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/personamanagmentlayer/pcl/customer-support-expert)<a href="https://agentmods.dev/skills/personamanagmentlayer/pcl/customer-support-expert"><img src="https://agentmods.dev/badge/skills/personamanagmentlayer/pcl/customer-support-expert/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/personamanagmentlayer/pcl/customer-support-expert"><img src="https://agentmods.dev/badge/skills/personamanagmentlayer/pcl/customer-support-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00977 |
| Opus 5 | $0.00029 | $0.00489 |
| Sonnet 5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
customer-support-expert 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Support Expert
Build comprehensive customer support systems including ticketing, knowledge management, SLA tracking, and customer satisfaction analytics.
Learning Objectives
- Master helpdesk and ticketing systems
- Understand SLA management and escalation processes
- Implement knowledge base and self-service solutions
- Apply customer satisfaction measurement and analytics
- Navigate omnichannel support operations
Prerequisites
- Understanding of customer service principles
- Knowledge of ITIL or service desk frameworks
- Familiarity with support workflows and processes
- Experience with customer communication channels
Core Concepts
Helpdesk & Ticketing Systems
Centralized platforms for managing customer inquiries, tracking issues through resolution, automating workflows, and maintaining complete interaction history across support channels.
SLA Management
Service Level Agreement tracking that defines and monitors response and resolution times, escalation procedures, and ensures contractual support commitments are met.
Knowledge Base Management
Self-service repositories containing articles, FAQs, troubleshooting guides, and documentation that enable customers to resolve issues independently and support agents to find answers quickly.
Customer Satisfaction Measurement
Systems for collecting feedback through surveys (CSAT, NPS, CES), analyzing sentiment, tracking trends, and identifying improvement opportunities in support quality.
Omnichannel Support
Unified support experience across multiple channels (email, chat, phone, social media, mobile) with consistent information and seamless transitions between channels.
Best Practices
Ticketing System
- Use clear ticket categorization and tagging
- Implement automated ticket routing and assignment
- Set realistic SLAs based on priority and customer tier
- Track all customer interactions in tickets
- Use templates for common responses
- Implement escalation workflows
- Regular ticket queue monitoring
What ships with it
1 file 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.
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.
- 4d ago First seen · 171 lines · 58 tokens per session scan A 757f04d5f14f
customer-support-expert is a skill published in the GitHub repository personamanagmentlayer/pcl (40 stars, last pushed 2d ago), licensed Apache-2.0. It adds 58 tokens to every session and 977 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-09-05.
Other skills, from other repositories
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
mk:jira-jsm
JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: 'create JSM request', 'list service desks', 'SLA status for KEY', 'approve request KEY', 'list queue NAME'. Requires JSM-licensed tenant + agent role.…
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…