ai-dial-core: Command for Claude Code

.claude/commands/start-issue.md

start-issue is a command for Claude Code from epam/ai-dial-core. It costs 13 tokens per session (331 once invoked), scanned A, original, Apache-2.0.

A command that reads a GitHub issue, which is a tracked task or bug, and creates a new Git branch for it from the latest development code. It also summarizes the issue before handing the work over.

In plain words
What is it for?
Use it to start work on an issue in the epam/ai-dial-core repository after GitHub CLI is installed and signed in.
Why use it?
It avoids manually copying issue details and preparing the starting branch. It gives the work a branch name based on whether the issue is a fix, feature, or maintenance task.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is epam/ai-dial-core's own configuration. It tells Claude Code how to work on ai-dial-core itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-dial-core configures →

Reuse

Borrowing it

Nothing to install: this file belongs to epam/ai-dial-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/epam/ai-dial-core/development/.claude/commands/start-issue.md
Clone the repo
git clone --depth 1 https://github.com/epam/ai-dial-core

Made for: Claude Code.

Wrote 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.

agentmods badge for start-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/epam/ai-dial-core/start-issue/github.svg)](https://agentmods.dev/commands/epam/ai-dial-core/start-issue)
Your own site
<a href="https://agentmods.dev/commands/epam/ai-dial-core/start-issue"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/start-issue/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.

agentmods 80×15 button for start-issue

Your own site · 80×15
<a href="https://agentmods.dev/commands/epam/ai-dial-core/start-issue"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/start-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00331
Opus 5.5 $0.00005 $0.00132
Sonnet 5.5 $0.00003 $0.00066
Haiku 4.5 $0.00001 $0.00033

Measured 1mo ago against content hash ad3ed1ccd8f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

start-issue 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.

.claude/commands/start-issue.md · 37 lines

What it actually says

Start a GitHub issue

Issue number: $ARGUMENTS

Prerequisites

Steps

  1. Fetch the issue from GitHub:

    gh issue view $ARGUMENTS --repo epam/ai-dial-core --json title,body,labels,assignees,comments
    

    Read it. Summarize to the user in 2-3 sentences.

  2. Determine the branch prefix from the issue title/labels:

    • fix/ — bugs, errors, incorrect behavior
    • feat/ — new features, enhancements
    • chore/ — maintenance, CI, deps, docs
  3. Create the branch from latest development:

    git stash  # if there are uncommitted changes
    git checkout development
    git pull origin development
    git checkout -b {prefix}/issue-$ARGUMENTS
    

    If the branch already exists, ask the user whether to reuse or recreate it.

After the branch is ready, hand off to the user for implementation. Use /finish-issue when ready to commit and /open-pr when ready to push and open a PR.

Changes

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.

  1. 1mo ago First seen · 37 lines · 13 tokens per session scan A ad3ed1ccd8f0

Subscribe to this mod's changes

start-issue is a command published in the GitHub repository epam/ai-dial-core (661 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 331 once invoked, about $0.0001 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.