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-chat/monitor-cigit 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/commands/epam/ai-dial-chat/monitor-ci)<a href="https://agentmods.dev/commands/epam/ai-dial-chat/monitor-ci"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-chat/monitor-ci.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.00000 | $0.06954 |
| Opus 5 | $0.00000 | $0.03477 |
| Sonnet 5 | $0.00000 | $0.01391 |
| Haiku 4.5 | $0.00000 | $0.00695 |
Grade A, and why
monitor-ci 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.
This is a copy
94% identical to monitor-ci — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 641 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor CI Command
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.
Context
- Current Branch: !
git branch --show-current - Current Commit: !
git rev-parse --short HEAD - Remote Status: !
git status -sb | head -1
User Instructions
Important: If user provides specific instructions, respect them over default behaviors described below.
Configuration Defaults
| Setting | Default | Description |
|---|---|---|
--max-cycles |
10 | Maximum agent-initiated CI Attempt cycles before timeout |
--timeout |
120 | Maximum duration in minutes |
--verbosity |
medium | Output level: minimal, medium, verbose |
--branch |
(auto-detect) | Branch to monitor |
--subagent-timeout |
30 | Subagent polling timeout in minutes |
--fresh |
false | Ignore previous context, start fresh |
--auto-fix-workflow |
false | Attempt common fixes for pre-CI-Attempt failures (e.g., lockfile updates) |
--new-cipe-timeout |
10 | Minutes to wait for new CI Attempt after action |
--local-verify-attempts |
3 | Max local verification + enhance cycles before pushing to CI |
Nx Cloud Connection Check
CRITICAL: Before starting the monitoring loop, verify the workspace is connected to Nx Cloud.
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 · 641 lines · 0 tokens per session scan A 1b397b81a186
monitor-ci is a command published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,954 tokens. A static security scan graded it A with 0 findings. It is 94% identical to monitor-ci, differing in 16 lines, and is treated as a copy.
Other commands, from other repositories
pr-check
Run all local CI checks before creating a PR.
finish-issue
Run pre-commit checks and commit the issue work on the current branch.
open-pr
Push the current issue branch and open a pull request against development.
start-issue
Fetch a GitHub issue and create a branch from latest development.
ci-sentinel
Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…