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 agentmods add skills/cbrock84/headcount/support-operationsnpx skills add cbrock84/headcount --skill support-operationsgit clone --depth 1 https://github.com/cbrock84/headcountWrote 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/cbrock84/headcount/support-operations)<a href="https://agentmods.dev/skills/cbrock84/headcount/support-operations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/support-operations.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.00829 |
| Opus 5 | $0.00039 | $0.00415 |
| Sonnet 5 | $0.00015 | $0.00166 |
| Haiku 4.5 | $0.00008 | $0.00083 |
Grade A, and why
support-operations 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 today.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support operations
Understand demand before designing supply
Categorize a real sample of recent contacts — a few hundred, read individually, not a report. Almost every support operation finds the same shape: a small number of causes generating most of the volume, and most of those are preventable rather than answerable.
That analysis decides everything downstream. Staffing to demand you have not examined means staffing to demand you could have eliminated.
The hierarchy of handling
In order of cost, cheapest first. Push volume up this list rather than getting faster at the bottom:
- Eliminate — fix the product defect or confusing flow generating the contact.
- Deflect — answer it in the interface at the moment of confusion, not in a help center nobody visits.
- Self-serve — findable documentation for people who go looking.
- Automate — genuine resolution of routine requests, not a bot that stalls people before a human.
- Assist — a person.
Most support improvement programs work on level 5 exclusively, because it is the visible one.
Channels
Pick by what the work needs, not by what is fashionable. Asynchronous channels are cheaper and better for anything requiring investigation. Synchronous channels are worth their cost for urgency, high-value accounts, and anything where a customer is stuck mid-task.
Every channel you open must be staffed to its expectation. An unstaffed live-chat widget is worse than no chat.
Service levels
Set by severity and customer tier, published internally, and — this is the part usually missing — checked against actual capacity before being promised. A commitment the staffing cannot meet is a commitment to fail visibly.
Measure first response and time to resolution separately. They have different causes: first response is a staffing problem, resolution is usually a product or escalation problem.
Metrics that mean something
- Contacts per active customer, trending. The only metric that captures whether the product is getting better rather than the team getting faster.
- First-contact resolution — reopens are the honest signal.
- Backlog age distribution, not average age. Averages hide the tickets rotting at the back, and those are the ones that become complaints.
- Customer-effort, asked at resolution.
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.
- today Changed · +17 lines 59a89e6b8bd1
- 4d ago First seen · 71 lines · 77 tokens per session scan A 1b4d91d82ddf
support-operations is a skill published in the GitHub repository cbrock84/headcount (1,176 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 829 once invoked, about $0.0004 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-30.
Other skills, from other repositories
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
security-assessment
Vulnerability review, threat modeling, OWASP patterns, and secure coding assessment. Use when reviewing code security, designing secure systems, performing threat analysis, or validating security implementations.
writing-skills
Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill doesn't work" complaints.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
extensions
Report which extensions the connected NeatContext context expects, and whether this machine provides them. Use when the user asks what a context can reach, why an extension tool is missing, or how to connect one here.
user-story-map
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.