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 instructions/epam/ai-dial-core/claude-mdgit clone --depth 1 https://github.com/epam/ai-dial-coreWrote 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/instructions/epam/ai-dial-core/claude-md)<a href="https://agentmods.dev/instructions/epam/ai-dial-core/claude-md"><img src="https://agentmods.dev/badge/instructions/epam/ai-dial-core/claude-md.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.01214 | $0.01214 |
| Opus 5 | $0.00607 | $0.00607 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
ai-dial-core CLAUDE.md 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build & Run
GitHub credentials are required for the private JClouds Maven package (hosted on GitHub Packages):
# Set credentials via environment variables
export GPR_USERNAME=<github_user>
export GPR_PASSWORD=<github_token>
# Build (skip tests)
./gradlew build -x test
# Run all tests
./gradlew test
# Run tests for a specific module
./gradlew :server:test
# Run a single test class
./gradlew :server:test --tests "com.epam.aidial.core.server.ResourceApiTest"
# Run a single test method
./gradlew :server:test --tests "com.epam.aidial.core.server.ResourceApiTest.testWorkflow"
# Checkstyle
./gradlew checkstyleMain checkstyleTest
# Run locally
./gradlew :server:run
At runtime, set AIDIAL_SETTINGS env var pointing to a JSON settings file (see sample/aidial.settings.json).
Architecture
AI DIAL Core is an HTTP reverse proxy / API gateway for LLMs built on Java 21 + Eclipse Vert.x (reactive, non-blocking). It exposes an OpenAI-compatible API and routes requests to backend AI providers (Azure OpenAI, AWS, GCP, etc.).
Gradle Modules
| Module | Root Package | Responsibility |
|---|---|---|
config |
com.epam.aidial.core.config |
POJOs for the dynamic config (Config, Model, Application, Key, Role, Route, Interceptor, ToolSet, Upstream, Limit, …) + JSON validation |
storage |
com.epam.aidial.core.storage |
Blob storage abstraction via Apache JClouds (S3, GCS, Azure Blob, filesystem), Redis-backed resource service, resource descriptors, locking |
credentials |
com.epam.aidial.core.credentials |
OAuth2 token management, AES credential encryption, KMS integration (AWS/Azure/GCP) |
server |
com.epam.aidial.core.server |
Entry point (AiDial.java), HTTP proxy engine (Proxy.java), all controllers, services, security, rate limiting, upstream load balancing, telemetry |
openapi-annotations |
com.epam.aidial.core.openapi.annotations |
Custom annotations for describing OpenAPI operations, schemas, parameters, responses, headers, extensions, and reusable response profiles. |
openapi-generator |
com.epam.aidial.core.openapi |
Generates and validates the OpenAPI 3.0 specification from controller annotations, builds schemas and responses, assembles the specification, and merges it with the manually maintained OpenAPI document. |
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.
- 5d ago First seen · 92 lines · 1,214 tokens per session scan A 29ee800eedde
ai-dial-core CLAUDE.md is an instructions file published in the GitHub repository epam/ai-dial-core (658 stars, last pushed today), licensed Apache-2.0. It adds 1,214 tokens to every session, about $0.0061 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 instructions, from other repositories
ai-dial-chat AGENTS.md
AGENTS.md instructions for epam/ai-dial-chat, covering general guidelines for working with nx, scaffolding & generators, when to use nxdocs, architecture context and library isolation.
ai-dial-chat all-ts.instructions.md
Instructions for epam/ai-dial-chat, a project described as: A default UI for AI DIAL.
ai-dial-chat all-tsx.instructions.md
Instructions for epam/ai-dial-chat, a project described as: A default UI for AI DIAL.
ai-dial-chat apps.instructions.md
Instructions for epam/ai-dial-chat, a project described as: A default UI for AI DIAL.
ai-dial-chat lib-styling.instructions.md
Instructions for epam/ai-dial-chat, a project described as: A default UI for AI DIAL.
ai-dial-chat libs.instructions.md
Instructions for epam/ai-dial-chat, a project described as: A default UI for AI DIAL.