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.
npx agentmods add commands/conectlens/lenserfight/monitor-cigit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/commands/conectlens/lenserfight/monitor-ci)<a href="https://agentmods.dev/commands/conectlens/lenserfight/monitor-ci"><img src="https://agentmods.dev/badge/commands/conectlens/lenserfight/monitor-ci.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03608 |
| Opus 5 | $0.00000 | $0.01804 |
| Sonnet 5 | $0.00000 | $0.00722 |
| Haiku 4.5 | $0.00000 | $0.00361 |
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 yesterday.
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
89% identical to monitor-ci — 58 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 — 293 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 subagents to interact with Nx Cloud, run deterministic decision scripts, and take action 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 |
--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
Before starting the monitoring loop, verify the workspace is connected to Nx Cloud. Without this connection, no CI data is available and the entire skill is inoperable.
Step 0: Verify Nx Cloud Connection
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.
- yesterday First seen · 293 lines · 0 tokens per session scan A 40724362e9f7
monitor-ci is a command published in the GitHub repository conectlens/lenserfight (19 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,608 tokens. A static security scan graded it A with 0 findings. It is 89% identical to monitor-ci, differing in 58 lines, and is treated as a copy.
Other commands, from other repositories
setup-ci
Tu es un DevOps Engineer expert. Tu dois configurer un pipeline CI/CD adapté aux technologies du projet, en suivant les bonnes pratiques.
docker-cicd-pipeline
Du bist ein Docker CI/CD Experte. Du musst eine vollständige Pipeline zum Bauen, Testen, Scannen und Deployen von Docker-Images generieren.
deploy-setup
Setup CI/CD pipeline for Ansible automation.
deploy
Deploy application with pre/post-deploy checks.
coolify-deploy
Deploy application to Coolify.
status
Show the current status of a NanoResearch workspace.