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 commands/epam/ai-dial-core/finish-issuegit 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/commands/epam/ai-dial-core/finish-issue)<a href="https://agentmods.dev/commands/epam/ai-dial-core/finish-issue"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/finish-issue.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.1 | $0.00015 | $0.00304 |
| Opus 5 | $0.00008 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
finish-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 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.
What it actually says
Finish a GitHub issue (checks + commit)
Run on the issue branch created by /start-issue. Derive the issue number and commit type from the branch name (e.g., fix/issue-1234 → type fix, issue 1234).
Steps
-
Run checkstyle and the full test suite to catch any cross-module regressions:
./gradlew checkstyleMain checkstyleTest ./gradlew testIf any check or test fails, stop. Investigate and fix the failures before staging or committing.
-
Stage only the files related to this issue. Do not commit unrelated files (local configs, IDE files, etc.). Inspect
git statusbefore staging. -
Commit using conventional commit format:
{type}: {description} #{issue_number}{type}matches the branch prefix (fix/feat/chore).{description}is derived from the GitHub issue title; refine only if needed for clarity or to fit the line length.
After the commit, stop and wait for the user. Use /open-pr to push and open a PR when ready.
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 · 28 lines · 15 tokens per session scan A 2afd63670e0c
finish-issue is a command published in the GitHub repository epam/ai-dial-core (658 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 304 once invoked, about $0.0001 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 commands, from other repositories
pr
Create a new branch, commit changes, push, create PR, and fix all failed checks (except claude review).
gen-commit-msg
Generate intelligent commit messages based on staged changes. Invoke with /gen-commit-msg.
ship
Commit all changes, push branch, create/update PR, and run local validation.
caveman-commit
Generate a terse caveman-style commit message for staged changes.
commit
Creates commits with Conventional Commits format (feat/fix/docs/refactor/test/chore), automatic scope detection, co-author attribution, and pre-commit hook compliance. Validates staged changes, generates descriptive messages focusing on the 'why', and prevents secrets or generated-only files from being committed.…
commit
../../.mastracode/commands/commit.md.