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 erphq/skills --skill customer-support-techgit clone --depth 1 https://github.com/erphq/skillsWrote 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/erphq/skills/customer-support-tech)<a href="https://agentmods.dev/skills/erphq/skills/customer-support-tech"><img src="https://agentmods.dev/badge/skills/erphq/skills/customer-support-tech/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/erphq/skills/customer-support-tech"><img src="https://agentmods.dev/badge/skills/erphq/skills/customer-support-tech.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00061 | $0.01876 |
| Opus 5.5 | $0.00024 | $0.00750 |
| Sonnet 5.5 | $0.00012 | $0.00375 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
customer-support-tech 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sector: Customer Support Tech
What This Sector Is
Customer support technology runs the post-sales customer-facing workflow — tickets, live chat, voice, knowledge bases, customer satisfaction measurement, and (increasingly) AI-driven deflection + automation. ~$30B global TAM for contact center + helpdesk combined, with strong LLM-driven disruption underway 2024–2026.
Buyers: VP CX / VP Support / CCO, sometimes split with IT for contact-center infrastructure. Mid-market + enterprise: 6–12 month procurement cycles; SMB: weeks. Category has seen significant take-private activity (Zendesk, Qualtrics, Five9 explored deals).
Sub-categories
Helpdesk / Customer Service Platforms
Public: Freshworks (FRSH), Salesforce Service Cloud (CRM), HubSpot Service Hub (HUBS), ServiceNow CSM (NOW).
Private (take-privates): Zendesk → Permira private 2022, Gladly (private), Help Scout (private), Intercom (private though revenue significant), Zoho Desk (private).
Contact Center as a Service (CCaaS)
Public: NICE (NICE) — enterprise leader with multi-product CX suite; Five9 (FIVN) cloud-native CCaaS; 8x8 (EGHT) unified-communications + contact-center.
Private / taken private: Genesys (Permira private), Talkdesk (private), Cisco Webex Contact Center (CSCO), Avaya (went bankrupt + re-emerged).
Category has consolidation: Genesys (take-private), UCaaS + CCaaS convergence (8x8, RingCentral).
Unified Communications (UCaaS, adjacent)
Public: RingCentral (RNG), Zoom (ZM) Zoom Phone + Contact Center, 8x8 (EGHT), Twilio (TWLO) programmable voice/SMS/video.
Private: Dialpad, Webex (Cisco subset), TeleSign (Twilio portfolio).
Voice of Customer / Experience Management
Public: NICE (NICE) has workforce engagement + feedback; Sprinklr (SPRK) CX management.
Private / taken private: Qualtrics → Silver Lake + CPPIB private 2023, Medallia (Thoma Bravo private 2021), Delighted (Qualtrics), UserTesting (Thoma Bravo private 2022).
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.
- 1mo ago First seen · 161 lines · 61 tokens per session scan A 543d1ff56460
customer-support-tech is a skill published in the GitHub repository erphq/skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,876 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
keep-the-why
In a project with a .keep-the-why, or when asked about Keep the Why or to set it up - extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.…
review
Adversarial fresh-context review and risk check of an increment before it ships; every finding cites path:line and is re-verified. Use for "review", "qa", "quality check", "critique this".
sw-do
Work a SpecWeave increment task by task - claim, implement inside the task's Files, test, commit, done with evidence - then verify and close. Use for "implement", "continue", "keep going".
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.
done
Close a SpecWeave increment - every task done or skipped, specweave verify green, a fresh-context review, then specweave complete. Use for "close it", "we are done", "finish up".
plan
Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.