Borrowing it
Nothing to install: this file belongs to leboncoin/spark-web. 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/leboncoin/spark-web/main/.cursor/agents/ci-monitor-subagent.mdgit clone --depth 1 https://github.com/leboncoin/spark-webWrote 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/leboncoin/spark-web/ci-monitor-subagent)<a href="https://agentmods.dev/agents/leboncoin/spark-web/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/leboncoin/spark-web/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/leboncoin/spark-web/ci-monitor-subagent"><img src="https://agentmods.dev/badge/agents/leboncoin/spark-web/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.5 | $0.00014 | $0.02264 |
| Sonnet 5.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 1mo 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
100% identical to ci-monitor-subagent — 0 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 — 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.
- 1mo ago First seen · 612 lines · 36 tokens per session scan A 5b28159950b2
ci-monitor-subagent is an agent published in the GitHub repository leboncoin/spark-web (94 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 5,659 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ci-monitor-subagent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
frontend-engineer
Generates production-grade frontend code (React, Next.js, Vue, Blade+Alpine, vanilla HTML, Astro) with anti-AI-slop discipline. Dispatched by /ux-design, /ux-component, /ux-dashboard, /ux-fix. Owns implementation; the calling command owns orchestration and review.
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.
devops-engineer
Infrastructure and Operations architect. Specialist in CI/CD, IaC, Global Distribution, and Disaster Recovery.
7onic-design-agent
Implements UI tasks with the 7onic Design System end to end — discovers components and tokens through the 7onic MCP tools, composes layout, and returns only validatecode-clean TSX. Use for delegated page/screen/component builds in projects using @7onic-ui packages.
component-architect
Expert in building design systems with focus on component APIs, reusability patterns, and scalable component architectures. Creates flexible, composable, accessible-by-default components.
frontend-engineer
React/Next.js/TypeScript frontend implementation. Use for UI, components, styling work.