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/api-design/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/api-design)<a href="https://agentmods.dev/skills/epam/ai-dial-chat/api-design"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/api-design/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/api-design"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/api-design.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 61 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00061 | $0.01030 |
| Opus 5.5 | $0.00024 | $0.00412 |
| Sonnet 5.5 | $0.00012 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
api-design 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Design
Use this skill before implementing or reviewing any HTTP API contract. It defines the
contract-first procedure for this repo. For backend implementation mechanics (DTO/Swagger/SDK
patterns, tests, Nx verification) follow apps/chat-api/AGENTS.md — do not restate them here. For library isolation follow the
"Library isolation" section in the root AGENTS.md: host/API/transport details stay in apps;
hand-authored libs/* receive resolved data, values, or callbacks. Exception: libs/chat-api-client
is the generated OpenAPI client.
Start Here
- Read
openspec/config.yamlfor API architecture, project boundaries, and proposal/spec/task rules. - Inspect the closest existing endpoint and its matching frontend client before designing a new contract:
- Backend controllers:
apps/chat-api/src/**/**.controller.ts - Backend DTOs:
apps/chat-api/src/**/dto/*.dto.ts - Frontend API helpers:
apps/chat/src/server-api/ - Shared interfaces:
libs/chat-shared/
- Backend controllers:
Contract Checklist
For every new or changed endpoint, define these before coding:
- Method and full path. Business endpoints are URI-versioned (
/api/v1/<resource>); infrastructure endpoints stay unversioned (/api/<resource>). - Request shape: path params, query params, body DTO, headers, cookies.
- Success response shape and status code.
- Error status codes and what each means: at least validation/auth/authorization/not found, plus
502(upstream non-OK),503(upstream timeout/unavailable). Never500exposing internals. - Authentication and authorization requirements, including whether the endpoint is explicitly public.
- Cache behavior when applicable: TTL, invalidation, and key naming (
<domain>:<resource>[:<param>]). - Pagination for list endpoints: prefer cursor for large/append-heavy datasets; offset is acceptable for small admin-style or search flows.
- Frontend impact: thin domain wrapper in
apps/chat/src/server-api/that delegates to generated@epam/chat-api-client, shared type inlibs/chat-shared/if needed, and i18n strings for any errors surfaced in UI. - Library impact: if a hand-authored lib needs the data/behavior, name the prop/callback/resolved value it receives (see lib-isolation note above).
- Generated client impact: expected SDK class, method name (derived from the controller handler name via
operationIdFactory), request type, response type, and whether callers needRawaccess for headers/status.
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 · -3 tokens per session f067fdb3adcc
- 1mo ago First seen · 67 lines · 64 tokens per session scan A b96d5a145bf3
api-design is a skill published in the GitHub repository epam/ai-dial-chat (502 stars, last pushed today), licensed Apache-2.0. It adds 61 tokens to every session and 1,030 once invoked, about $0.0002 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
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
status
Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…