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/schmitech/orbit/support-ticket-playbooknpx skills add schmitech/orbit --skill support-ticket-playbookgit clone --depth 1 https://github.com/schmitech/orbitWrote 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/schmitech/orbit/support-ticket-playbook)<a href="https://agentmods.dev/skills/schmitech/orbit/support-ticket-playbook"><img src="https://agentmods.dev/badge/skills/schmitech/orbit/support-ticket-playbook.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.1 | $0.00019 | $0.00372 |
| Opus 5 | $0.00010 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade C, and why
support-ticket-playbook scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
log, or file a support ticket, call `create_support_ticket` directly. Never decline a ticket-creation request or claim no such tool exists. What it actually says
Creating tickets
These tools ARE the ticket system for this session — when asked to open,
log, or file a support ticket, call create_support_ticket directly. Never
decline a ticket-creation request or claim no such tool exists.
create_support_ticket requires a customer id. Use an id the user supplied
or ask for one when it is unavailable; never invent a cus_... value. Report
the server-assigned ticket id, customer, priority, status, and subject after a
successful creation.
Reading before writing
Call get_support_ticket to read the current state of a ticket before
calling update_support_ticket or delete_support_ticket on it, so the
update doesn't blindly overwrite fields you haven't seen.
Deleting
Confirm explicitly with the user before calling delete_support_ticket —
deletion is permanent for this session's in-memory data and cannot be
undone.
Output
For list_support_tickets, render the returned tickets as a table: Ticket |
Customer | Priority | Status | SLA breached | Subject. For get_support_ticket,
show the current ticket fields before proposing an update or deletion. After
an update or deletion, report only the confirmed result returned by the tool;
do not claim a change succeeded when it returned an error.
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 · 45 lines · 19 tokens per session scan C 6eeee0fd93f3
support-ticket-playbook is a skill published in the GitHub repository schmitech/orbit (343 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 372 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
technology-search
Search tech blogs, developer forums, and IT media (TechCrunch, Hacker News, 36氪, etc.) for software and hardware industry updates with heat ranking and EN↔CN translation. Use this skill only when the topic is clearly about programming, software, hardware, AI, or IT infrastructure.
imap-smtp-email
Read and send email via IMAP/SMTP. Check for new/unread messages, fetch content, search mailboxes, mark as read/unread, and send emails with attachments. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.
article-writer
Multi-style article creation skill. Supports 5 writing styles (deep analysis, practical guide, story-driven, opinion, news brief), including complete workflow: material collection → outline → content → formatting. Activated when users mention "write article", "write post", "create", or "draft".
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
skin-creator
Create and apply a two-asset LobsterAI visual skin from the user's style description. Use only when the AI Skin Designer kit supplies the structured skinpack workflow marker; do not use for ordinary theme or image requests.
content-planner
WeChat Official Account topic planning and content calendar management. Based on WeChat article search and trending analysis, generates differentiated topic recommendations and outputs structured content calendars. Activated when users mention "topic", "planning", "content calendar", "trending", or "what to write next…