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/open-prgit 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/open-pr)<a href="https://agentmods.dev/commands/epam/ai-dial-core/open-pr"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/open-pr.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.00013 | $0.00296 |
| Opus 5 | $0.00006 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
open-pr 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.
What it actually says
Open a pull request
Run on the issue branch after committing with /finish-issue. Derive the issue number and commit type from the branch name (e.g., fix/issue-1234 → type fix, issue 1234).
Steps
-
Push the current branch:
git push -u origin {branch} -
Create the PR against
development:gh pr create --base development --title "{type}: {Title from issue} #{issue_number}" --body "$(cat <<'EOF' {1-3 sentence summary of changes} ### Applicable issues - fixes #{issue_number} ### Description of changes {Bullet list of what changed and why} ### Checklist - [X] Title of the pull request follows [Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/) By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. EOF )"
Important
- Keep the PR title under 70 characters.
- Confirm the branch is up to date with the latest commits before pushing.
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 · 42 lines · 13 tokens per session scan A f77f2c93ebe9
open-pr is a command published in the GitHub repository epam/ai-dial-core (658 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 296 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
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
/opsx-explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
/opsx-propose
Propose a new change - create it and generate all artifacts in one step.
/opsx-archive
Archive a completed change in the experimental workflow.
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.