monitor-ci

monitor-ci is a command for Cursor from nrwl/nx-console. It costs 0 tokens per session (6,985 once invoked), scanned A, original, MIT.

A command for monitoring Nx Cloud CI pipelines, which automatically build and test code on a remote service. It coordinates a helper agent that polls execution status and can handle selected self-healing fixes.

In plain words
What is it for?
Use it to monitor a branch's CI runs, wait for new attempts after actions, run local verification, and optionally apply common pre-run workflow fixes.
Why use it?
It keeps track of CI attempts over time and helps determine whether a failure needs another automated action or manual attention.

Command 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 commands/nrwl/nx-console/monitor-ci
Clone the repo
git clone --depth 1 https://github.com/nrwl/nx-console

Made for: Cursor.

Wrote 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.

agentmods badge for monitor-ci

README.md
[![agentmods](https://agentmods.dev/badge/commands/nrwl/nx-console/monitor-ci.svg)](https://agentmods.dev/commands/nrwl/nx-console/monitor-ci)
Your own site
<a href="https://agentmods.dev/commands/nrwl/nx-console/monitor-ci"><img src="https://agentmods.dev/badge/commands/nrwl/nx-console/monitor-ci.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,985 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00000 $0.06985
Opus 5 $0.00000 $0.03492
Sonnet 5 $0.00000 $0.01397
Haiku 4.5 $0.00000 $0.00698

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

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/commands/monitor-ci.md · 649 lines

How it starts

The opening of the file, as written. The whole thing — 649 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.

Read the full file on GitHub · 649 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. 4d ago First seen · 649 lines · 0 tokens per session scan A 5006d7846821

Subscribe to this mod's changes

monitor-ci is a command published in the GitHub repository nrwl/nx-console (1,412 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,985 tokens. 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.