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/dial-docsnpx skills add epam/ai-dial-chat --skill dial-docsgit 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/dial-docs)<a href="https://agentmods.dev/skills/epam/ai-dial-chat/dial-docs"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/dial-docs.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.00108 | $0.00791 |
| Opus 5 | $0.00054 | $0.00396 |
| Sonnet 5 | $0.00022 | $0.00158 |
| Haiku 4.5 | $0.00011 | $0.00079 |
Grade A, and why
dial-docs 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 4d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DIAL Docs
Ground-truth design docs live in docs/. This skill is the index. Open only the doc that matches your task — don't read all of them.
Index
| Doc | Read it when |
|---|---|
docs/architecture.md |
Orienting on the overall app: structure, layers, major decisions. |
docs/technical-requirements.md |
You need the product/technical requirements behind a feature. |
docs/auth/auth-bff-encrypted-cookie.md |
Changing the auth flow: stateless BFF, OIDC login/callback, encrypted session cookie, transparent refresh, federated logout, cross-pod stateless decryption. |
docs/auth/testing-current-auth-implementation.md |
Writing or running auth tests: what exists today (GET /api/v1/auth/me, global SessionGuard, refresh) and how to exercise it. |
docs/auth/auth-diagrams/ |
You need the picture: Mermaid .mmd + .svg for architecture, provider registry, login, refresh, logout, cross-pod, cookie structure. |
docs/legacy-chat-migration-guide.md |
Moving a deployment from the legacy DIAL Chat (0.x) to 1.0: what changed, the checklist, and the legacy → new environment-variable mapping. |
docs/theme-customization.md |
Theming: the themes service and config.json format, the color tokens the app reads, logos and favicon, the light/dark/system picker, legacy theme migration. |
docs/chat-overlay-migration-guide.md |
Embedding the chat: the overlay package, postMessage protocol and handshake, OverlayFeature flags, and migrating from the legacy @epam/ai-dial-overlay. |
docs/responses-api-integration.md |
Working on completions dispatch: how deployments declaring responses_api are routed and normalized. |
apps/chat-api/README.md |
The full environment-variable reference: every supported variable, its default, and its effect. apps/chat-api/.env.template is the annotated source. |
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.
- 4d ago First seen · 33 lines · 108 tokens per session scan A 9b62717d970c
dial-docs is a skill published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It adds 108 tokens to every session and 791 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
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…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…