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 skills add nrwl/nx-ai-agents-config --skill nx-cloud-ci-failure-reviewgit clone --depth 1 https://github.com/nrwl/nx-ai-agents-configWrote 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/skills/nrwl/nx-ai-agents-config/nx-cloud-ci-failure-review)<a href="https://agentmods.dev/skills/nrwl/nx-ai-agents-config/nx-cloud-ci-failure-review"><img src="https://agentmods.dev/badge/skills/nrwl/nx-ai-agents-config/nx-cloud-ci-failure-review/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/skills/nrwl/nx-ai-agents-config/nx-cloud-ci-failure-review"><img src="https://agentmods.dev/badge/skills/nrwl/nx-ai-agents-config/nx-cloud-ci-failure-review.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.00000 | $0.01248 |
| Opus 5.5 | $0.00000 | $0.00499 |
| Sonnet 5.5 | $0.00000 | $0.00250 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
nx-cloud-ci-failure-review 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nx Cloud CI failure review
Requires the nx-cloud-api skill for all Nx Cloud reads. This workflow is read-only.
Reduce failed pipelines to a small set of diagnostic groups. A failed pipeline does not prove that an agent or platform caused the failure. Classify each group only at the level the evidence supports.
Scope and collection
Use focused investigation mode when the user supplies one or more CIPE or run-group links. Fetch those exact records first. Follow their returned run-group, run, task, and workflow links. Compare the supplied executions directly. Do not run a broad time window or build a workspace-wide ranking unless the user asks for recurrence or scope. Keep cancellations that follow the named critical error as consequences, not separate root-cause groups.
Use review mode when the user asks for a workspace failure review. Review
failures from the last 24 hours by default. CIPE and run-group list filters use
createdAt, not failure time. Query a 30-hour creation window to cover the maximum
normal six-hour CI duration. State the intended 24-hour review period and the
30-hour creation window.
Query statuses=FAILED, statuses=TIMED_OUT, and statuses=CANCELED (the
cipes filter accepts only terminal statuses). State the
branches, CI contexts, statuses, endpoints, and record counts. Ask before widening
the window or mixing unrelated repositories/workspaces.
Use nx-cloud-api (npx nx-cloud api) for every read. Inspect the live
schemas with --describe for cipes, run-groups, run-groups/{runGroupId},
runs, runs/{runId}/tasks, and the linked steps and instances endpoints.
Use --list-operations to confirm the routes; the public API has no separate
workflow routes. Reach child records by following returned links. Start with supplied CIPEs in focused investigation mode. Start with failed CIPEs
and their linked run groups in review mode. Use only live documented filters and
fields. Fetch one narrow page first and check nextCursor before continuing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · +4 lines 9b691c14f93d
- 16d ago First seen · 125 lines · 0 tokens per session scan A 3c43fbaea1bf
nx-cloud-ci-failure-review is a skill published in the GitHub repository nrwl/nx-ai-agents-config (29 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,248 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-10-02.
Other skills, from other repositories
atmos-lint
Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.
cpln
Writes cpln CLI commands and workflows for Control Plane. Use when the user asks about cpln login, cpln apply, cpln workload, CLI or CI/CD deploys, container debugging with cpln exec/logs, or any cpln resource command.
failure-diagnosis
Diagnose deployment failures, container crashes, and networking issues using structured pattern matching on logs and container state. Use when a deployment fails, a container crashes or exits unexpectedly, or the app is unreachable after deployment.
pstack
Project-local pstack validation router for chmonitor. Use when proving a dashboard, API, auth or security, PeerDB, alerts and webhooks, Helm and GitOps, deployment, or CLI change. Prefer CI checks and capture observable evidence instead of running heavy local builds.
platform-integration
Cross-layer platform integration skill covering end-to-end delivery flows, team onboarding, DORA metrics, cross-layer debugging, and platform health checks. Orchestrates across all platform layers (build, pipeline, registry, secrets, mesh, GitOps, progressive delivery) and owns gitops-promoter CRDs (PromotionStrategy…
diagnosing-azure-deployment-failures
Matches Azure deploy / CI / runtime failures against 56 documented gotchas with verified fixes (BCP258, AADSTS70021, sqlcmd-not-found, FC1-CLI-silent-fallback, functions-action outage, Kudu quick-succession abort, ACS dataLocation quirks, SSE timeouts, Container Apps idle-burn, SWA Authorization-header overwrite, and…