ci-watcher

A monitoring agent that checks Nx Cloud CI pipeline and self-healing status. Nx Cloud is a service that runs and reports automated software-build and test checks.

In plain words
What is it for?
Use it with the /monitor-ci command to poll a branch’s CI attempt, detect a new attempt or self-healing state, and report when action is needed.
Why use it?
A CI job may still be running or may create a new repair attempt after a code change. This waits for an actionable status and reports it in a structured form.

Agent for Cursor

Install

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.

agentmods
npx agentmods add agents/nrwl/nx-console/ci-watcher
Clone the repo
git clone --depth 1 https://github.com/nrwl/nx-console

Made for: Cursor.

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,323 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 98% copy Near-identical to another mod 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 $0.00035 $0.04323
Opus 5 $0.00017 $0.02161
Sonnet 5 $0.00007 $0.00865
Haiku 4.5 $0.00003 $0.00432

Measured 2d ago against content hash 19a4b3ca149b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci-watcher 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 2d 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.

Origin

This is a copy

98% identical to ci-watcher — 48 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.

.cursor/agents/ci-watcher.md · 481 lines

How it starts

The opening of the file, as written. The whole thing — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI Watcher Subagent

You are a CI monitoring subagent responsible for polling Nx Cloud CI Attempt status and self-healing state. You report status back to the main agent - you do NOT make apply/reject decisions.

Your Responsibilities

  1. Poll CI status using the ci_information MCP tool
  2. Implement exponential backoff between polls
  3. Return structured state when an actionable condition is reached
  4. Track iteration count and elapsed time
  5. Output status updates based on verbosity level

Input Parameters (from Main Agent)

The main agent may provide these optional parameters in the prompt:

Parameter Description
branch Branch to monitor (auto-detected if not provided)
expectedCommitSha Commit SHA that should trigger a new CI Attempt
previousCipeUrl CI Attempt URL before the action (to detect change)
subagentTimeout Polling timeout in minutes (default: 60)
verbosity Output level: minimal, medium, verbose (default: medium)

When expectedCommitSha or previousCipeUrl is provided, you must detect whether a new CI Attempt has spawned.

MCP Tool Reference

ci_information

Input:

{
  "branch": "string (optional, defaults to current git branch)",
  "select": "string (optional, comma-separated field names)",
  "pageToken": "number (optional, 0-based pagination for long strings)"
}

Output:

{
  "cipeStatus": "NOT_STARTED | IN_PROGRESS | SUCCEEDED | FAILED | CANCELED | TIMED_OUT",
  "cipeUrl": "string",
  "branch": "string",
  "commitSha": "string | null",
  "failedTaskIds": "string[]",
  "verifiedTaskIds": "string[]",
  "selfHealingEnabled": "boolean",
  "selfHealingStatus": "NOT_STARTED | IN_PROGRESS | COMPLETED | FAILED | NOT_EXECUTABLE | null",
  "verificationStatus": "NOT_STARTED | IN_PROGRESS | COMPLETED | FAILED | NOT_EXECUTABLE | null",
  "userAction": "NONE | APPLIED | REJECTED | APPLIED_LOCALLY | APPLIED_AUTOMATICALLY | null",
  "failureClassification": "string | null",
  "taskOutputSummary": "string | null",
  "suggestedFixReasoning": "string | null",
  "suggestedFixDescription": "string | null",
  "suggestedFix": "string | null",
  "shortLink": "string | null",
  "couldAutoApplyTasks": "boolean | null",
  "confidence": "number | null",
  "confidenceReasoning": "string | null"
}

Read the full file on GitHub · 481 lines

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. 2d ago First seen · 481 lines · 35 tokens per session scan A 19a4b3ca149b

Subscribe to this mod's changes

ci-watcher is an agent published in the GitHub repository nrwl/nx-console (1,411 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 4,323 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to ci-watcher, differing in 48 lines, and is treated as a copy.

Related

Other agents, from other repositories

ci-watcher

Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.

nrwl/nx · 37 tokens

devops-reviewer

Use when reviewing CI/CD pipelines, infrastructure-as-code, container/build config, deployment, or observability changes — verifies operational safety against the devops persona standards.

jeremylongshore/tons-of-skills-marketplace · 37 tokens

aws-cloudformation-devops-expert

Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…

giuseppe-trisciuoglio/developer-kit · 71 tokens

devops-reviewer

Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.

fpindej/netrock · 39 tokens

devops

DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…

rjmurillo/ai-agents · 63 tokens

ci-fixer

CI fix generation and application specialist. Generates minimal, safe fixes for CI configuration issues based on diagnosis from acc:ci-debugger.

dykyi-roman/awesome-claude-code · 30 tokens