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 Bevel-Software/Hexis --skill customer-escalationgit clone --depth 1 https://github.com/Bevel-Software/HexisWrote 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/bevel-software/hexis/customer-escalation)<a href="https://agentmods.dev/skills/bevel-software/hexis/customer-escalation"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/customer-escalation/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/bevel-software/hexis/customer-escalation"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/customer-escalation.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.00054 | $0.02480 |
| Opus 5.5 | $0.00022 | $0.00992 |
| Sonnet 5.5 | $0.00011 | $0.00496 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
customer-escalation 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 6d 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.
This is a copy
88% identical to customer-escalation — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
customer-escalation
Names like
~~chator~~project trackermean whichever tool of that kind is connected: a tool in one of your Hexis plugins, or one your agent has itself. The knowledge base is this workspace's knowledge base in Hexis, plus any other docs tool that is connected. When a source is not connected, skip it and say what you could not check.
Package a support issue into a structured escalation brief for engineering, product, or leadership. Gathers context, structures reproduction steps, assesses business impact, and identifies the right escalation target.
Usage
Ask your agent for the customer-escalation skill by name, or just describe the job and it will pick the skill up. Give it: [customer name or account]
Examples:
customer-escalation API returning 500 errors intermittently for Acme Corpcustomer-escalation Data export is missing rows — 3 customers reported this weekcustomer-escalation SSO login loop affecting all Enterprise customerscustomer-escalation Customer threatening to churn over missing audit log feature
Workflow
1. Understand the Issue
Parse the input and determine:
- What's broken or needed: The core technical or product issue
- Who's affected: Specific customer(s), segment, or all users
- How long: When did this start? How long has the customer been waiting?
- What's been tried: Any troubleshooting or workarounds attempted
- Why escalate now: What makes this need attention beyond normal support
Use the "When to Escalate vs. Handle in Support" criteria below to confirm this warrants escalation.
2. Gather Context
Pull together relevant information from available sources:
- ~~support platform: Related tickets, timeline of communications, previous troubleshooting
- ~~CRM (if connected): Account details, key contacts, previous escalations
- ~~chat: Internal discussions about this issue, similar reports from other customers
- ~~project tracker (if connected): Related bug reports or feature requests, engineering status
- knowledge base: Known issues or workarounds, relevant documentation
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.
- 6d ago First seen · 247 lines · 54 tokens per session scan A 7109560748f0
customer-escalation is a skill published in the GitHub repository Bevel-Software/Hexis (115 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 2,480 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to customer-escalation, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
coordinator
Take over as coordinator of the current LangWatch drive: read the live state from disk (the lane roster, the newest handover, the shape counters), report it, then work the handover's next action by writing manifests and spawning lanes. Replaces pasting a brief out of a handover document - the state is read, never…
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.