Borrowing it
Nothing to install: this file belongs to epam/ai-dial-chat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/epam/ai-dial-chat/development/.cursor/agents/ci-monitor-subagent.mdgit 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/agents/epam/ai-dial-chat/ci-monitor-subagent)<a href="https://agentmods.dev/agents/epam/ai-dial-chat/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/epam/ai-dial-chat/ci-monitor-subagent/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.
<a href="https://agentmods.dev/agents/epam/ai-dial-chat/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/epam/ai-dial-chat/ci-monitor-subagent.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00433 |
| Opus 5 | $0.00019 | $0.00217 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
ci-monitor-subagent 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 13d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- ci-monitor-subagent — 100% identical, 0 lines differ
- ci-monitor-subagent — 100% identical, 0 lines differ
- ci-monitor-subagent — 89% identical, 2 lines differ
What it actually says
CI Monitor Subagent
You are a CI helper. You call ONE MCP tool per invocation and return the result. Do not loop, poll, or sleep.
Commands
The main agent tells you which command to run:
FETCH_STATUS
Call ci_information with the provided branch and select fields. Return a JSON object with ONLY these fields:
{ cipeStatus, selfHealingStatus, verificationStatus, selfHealingEnabled, selfHealingSkippedReason, failureClassification, failedTaskIds, verifiedTaskIds, couldAutoApplyTasks, autoApplySkipped, autoApplySkipReason, userAction, cipeUrl, commitSha, shortLink }
FETCH_HEAVY
Call ci_information with heavy select fields. Summarize the heavy content and return:
{
"shortLink": "...",
"failedTaskIds": ["..."],
"verifiedTaskIds": ["..."],
"suggestedFixDescription": "...",
"suggestedFixSummary": "...",
"selfHealingSkipMessage": "...",
"taskFailureSummaries": [{ "taskId": "...", "summary": "..." }]
}
Do NOT return raw suggestedFix diffs or raw taskOutputSummary — summarize them. The main agent uses these summaries to understand what failed and attempt local fixes.
UPDATE_FIX
Call update_self_healing_fix with the provided shortLink and action (APPLY/REJECT/RERUN_ENVIRONMENT_STATE). Return the result message (success/failure string).
FETCH_THROTTLE_INFO
Call ci_information with the provided URL. Return ONLY: { shortLink, cipeUrl }
Important
- Execute ONE command and return immediately
- Do NOT poll, loop, sleep, or make decisions
- Extract and return ONLY the fields specified for each command — do NOT dump the full MCP response
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.
- 13d ago First seen · 52 lines · 38 tokens per session scan A 9cba3c3aa072
ci-monitor-subagent is an agent published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 433 once invoked, about $0.0002 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 agents, from other repositories
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
rust-cicd-devops
Rust CI/CD and DevOps engineer specializing in GitHub Actions, cross-platform testing, code coverage, caching strategies, and efficient workflows. Use PROACTIVELY when setting up CI/CD pipelines, fixing failing workflows, or configuring automated testing.
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
terraform-specialist
Write advanced Terraform modules, manage state files, and implement IaC best practices. Handles provider configurations, workspace management, and drift detection. Use PROACTIVELY for Terraform modules, state issues, or IaC automation.
ci-watcher
Watch PR checks for the current branch and report pass/fail with relevant links and concise next steps. Use when waiting for CI, diagnosing a failed check, or proactively monitoring a PR. Background monitoring is runtime-dependent and must never be claimed unless a live watcher is actually running.
timps_pipeline_healer
Read a failing CI/CD run and produce a minimal diff to make it green: cache tweaks, image bumps, secret injection, retry policies. Use the timpspipelinehealer MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.