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/epam/ai-dial-chat/create-ticketnpx skills add epam/ai-dial-chat --skill create-ticketgit 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.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.00105 | $0.04466 |
| Opus 5 | $0.00053 | $0.02233 |
| Sonnet 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 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 — 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.
- yesterday Changed · +1 lines 281af1bcf1b3
- 5d 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 (504 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 4,466 once invoked, about $0.0005 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
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…