Borrowing it
Nothing to install: this file belongs to epam/ai-dial-chat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/epam/ai-dial-chat/development/.claude/skills/create-ticket/SKILL.mdgit clone --depth 1 https://github.com/epam/ai-dial-chatWrote 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/epam/ai-dial-chat/create-ticket)<a href="https://agentmods.dev/skills/epam/ai-dial-chat/create-ticket"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/create-ticket/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/epam/ai-dial-chat/create-ticket"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/create-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00105 | $0.04466 |
| Opus 5.5 | $0.00042 | $0.01786 |
| Sonnet 5.5 | $0.00021 | $0.00893 |
| Haiku 4.5 | $0.00011 | $0.00447 |
Grade A, and why
create-ticket 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a GitHub issue in this repository. Guides the user through an interactive flow to gather all required information, then creates the issue via gh issue create.
Prerequisites
Before starting the flow, verify gh CLI is available and authenticated:
gh auth status
- If
ghis not installed → stop and tell the user: "GitHub CLI (gh) is required. Install it: https://cli.github.com/" - If not authenticated → stop and tell the user: "Run
gh auth loginto authenticate first." - If authenticated → proceed to Step 0
Usage: /create-ticket [type: description | from spec | <change-path> | update <#issue|url>]
Examples:
/create-ticket— fully interactive/create-ticket bug: login page crashes on Safari/create-ticket feature: add bulk delete for models/create-ticket task: refactor Sidebar for reuse in entity lists/create-ticket infra: add LOG_LEVEL to prod/create-ticket from spec— from the openspec changes on the current branch/create-ticket openspec/changes/archive/2026-06-15-file-dnd-overlay— from a specific change/create-ticket update #123— add details to an existing issue
Step 0 — Intent, Source & Args
First decide which of three modes applies, then parse the remaining args.
- Mode C — Update existing — the user references an existing issue:
update,#<number>, or a GitHub issue URL. → go to Update Existing Ticket below. - Mode B — From spec — the user says "from spec", "from the branch", "issue from current change", or passes an
openspec/changes/...folder path. → go to From Spec below, which drafts the Step 2 proposal, then continues at Step 1/3. - Mode A — From discussion (default) — anything else. Continue with arg parsing here.
Mode A arg parsing
If the user provided arguments after /create-ticket, parse them:
- Look for a type prefix:
bug:,feature:,task:,infra:(case-insensitive)bug:→ Bugfeature:→ Featuretask:→ Task (general engineering)infra:→ Task + forceinfra-tasklabel (shortcut for infra change)- If found → set issue type, use the rest as a seed for the title/description
- If not found → treat the entire arg string as a description seed and ask for type
- If no args at all → start fully interactive from Step 1
What ships with it
4 files 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 Changed · +1 lines 281af1bcf1b3
- 1mo ago First seen · 456 lines · 105 tokens per session scan A 0e04472eed91
create-ticket is a skill published in the GitHub repository epam/ai-dial-chat (502 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 4,466 once invoked, about $0.0004 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-08-30.
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.
company-mirror
Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.