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/hoavdc/codexkit/codexkit-support-ticket-summarizernpx skills add hoavdc/CodexKit --skill codexkit-support-ticket-summarizergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-support-ticket-summarizer)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-support-ticket-summarizer"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-support-ticket-summarizer.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.00049 | $0.00896 |
| Opus 5 | $0.00024 | $0.00448 |
| Sonnet 5 | $0.00010 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
codexkit-support-ticket-summarizer 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 yesterday.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support Ticket Summarizer
When to Use
- Condensing long customer support threads into a case summary.
- Preparing a handoff between support agents, engineering, success, or account teams.
- Reviewing a backlog of tickets for escalation patterns.
- Drafting a customer-safe response after understanding the issue.
Procedure
Step 1 - Identify The Customer Problem
Extract the customer's stated issue, affected product or service, timeline, and expected outcome.
Step 2 - Determine Impact And Urgency
Classify impact:
- blocker: customer cannot use a critical workflow
- degraded: workflow works with workaround or delay
- question: clarification, how-to, billing, or admin request
- feedback: product suggestion or sentiment
Step 3 - Summarize Evidence
Preserve important technical details, order IDs, screenshots mentioned, error messages, account tier, and prior troubleshooting.
Step 4 - Recommend Next Step
Suggest the next action for support, engineering, customer success, or billing. Do not promise resolution time unless provided.
Step 5 - Draft Response
Write a customer-facing response when requested. Keep it empathetic, specific, and honest about unknowns.
Inputs
| Input | Required | Format |
|---|---|---|
| Ticket or chat text | Yes | Thread, transcript, notes |
| Customer context | Recommended | Plan, segment, account owner |
| Current status | Optional | New, waiting, escalated, resolved |
| Internal constraints | Optional | SLA, support policy, escalation path |
Output
## Ticket Summary - [Ticket ID / Customer]
### Customer Issue
[Plain-language issue]
### Impact And Priority
[Impact level, urgency, rationale]
### Evidence
- [Relevant facts, error messages, dates]
### Work Done So Far
- [Troubleshooting steps]
### Recommended Next Step
| Owner | Action | Deadline / SLA | Notes |
|-------|--------|----------------|-------|
### Customer Response Draft
[Optional response]
Quality Criteria
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.
- yesterday First seen · 117 lines · 49 tokens per session scan A 036581d4336e
codexkit-support-ticket-summarizer is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 896 once invoked, about $0.0002 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
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
product-reviews
Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.
delivering-delegated-linear-issues
当用户明确要求领取、处理、批量清空或定时扫描 Linear 的 Delegated to Agent issue 时使用；按队列状态、领取竞争、交付路径和收尾四个阶段渐进读取。.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.