Nx Console is an editor interface for Nx and Lerna monorepos, which are code repositories containing multiple related projects managed together. It gives developers visual workflows for viewing workspace structure, running tasks, navigating task graphs, and supplying workspace context to AI tools. The catalogue entries extend its workflows through skills, agents, instructions, MCP integrations, settings, and commands.
Borrowing it
Nothing to install: this file belongs to nrwl/nx-console. 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/nrwl/nx-console/master/.cursor/agents/ci-monitor-subagent.mdgit clone --depth 1 https://github.com/nrwl/nx-consoleWrote 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/nrwl/nx-console/ci-monitor-subagent)<a href="https://agentmods.dev/agents/nrwl/nx-console/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/nrwl/nx-console/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/nrwl/nx-console/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/nrwl/nx-console/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.00036 | $0.05659 |
| Opus 5 | $0.00018 | $0.02830 |
| Sonnet 5 | $0.00007 | $0.01132 |
| Haiku 4.5 | $0.00004 | $0.00566 |
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 12d 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
1 near-identical copy found in the catalogue:
- ci-monitor-subagent — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 612 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Monitor 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
- Poll CI status using the
ci_informationMCP tool - Implement exponential backoff between polls
- Return structured state when an actionable condition is reached
- Track iteration count and elapsed time
- 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: 30) |
newCipeTimeout |
Minutes to wait for CI Attempt before returning no_new_cipe (default: 10) |
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",
"hints": "string[]"
}
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.
- 12d ago First seen · 612 lines · 36 tokens per session scan A 5b28159950b2
ci-monitor-subagent is an agent published in the GitHub repository nrwl/nx-console (1,414 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 5,659 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
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.