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.
git clone --depth 1 https://github.com/Rebell-Leader/SpatialAI_MCPWrote 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/rules/rebell-leader/spatialai_mcp/nextflow-debugging)<a href="https://agentmods.dev/rules/rebell-leader/spatialai_mcp/nextflow-debugging"><img src="https://agentmods.dev/badge/rules/rebell-leader/spatialai_mcp/nextflow-debugging/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/rules/rebell-leader/spatialai_mcp/nextflow-debugging"><img src="https://agentmods.dev/badge/rules/rebell-leader/spatialai_mcp/nextflow-debugging.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.00048 | $0.00553 |
| Opus 5.5 | $0.00019 | $0.00221 |
| Sonnet 5.5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
nextflow-debugging 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nextflow debugging
The server does not yet parse logs for you (analyze_nextflow_log is roadmap), so
triage the logs directly. Be systematic.
Steps
-
Find the failing task. From the run output, note the process name and the work directory hash (
work/ab/cdef...). The per-task files there are the ground truth:.command.sh— the exact command run..command.err/.command.out— stderr/stdout..command.log,.exitcode— exit status.
-
Classify the error by exit code / message:
- 137 / OOM-killed → memory limit. Increase the process
memorydirective or add a dynamic retry (memory { 8.GB * task.attempt }). - 127 / "command not found" → tool missing in the container; fix the component's engine/setup or the image.
- 126 / permission denied → executable bit / entrypoint issue.
- File/path errors → check channel wiring and input staging; confirm the
input file actually exists and matches the expected format
(run
validate_spatial_data). - Config/DSL errors → confirm DSL2 syntax; OpenProblems pipelines are DSL2.
- 137 / OOM-killed → memory limit. Increase the process
-
Add resilience where appropriate:
errorStrategy 'retry',maxRetries, and dynamic resources bytask.attempt. Don't paper over a real bug with retries. -
Reproduce in isolation. Re-run a single component with
viash runon the test data before re-running the whole pipeline. Use-resumeto avoid recomputing successful tasks. -
Validate inputs with
validate_spatial_data/analyze_spatial_metadatawhen the failure looks data-shaped (wrong format, missing elements, raw-vs-normalized mismatch).
Output
Report: the failing process, the root-cause class, the evidence (the log line), and the specific fix — plus whether it's a data problem, an environment problem, or a code problem.
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 · 50 lines · 48 tokens per session scan A 03289bfcdeca
nextflow-debugging is a cursor rule published in the GitHub repository Rebell-Leader/SpatialAI_MCP (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 553 once invoked, about $0.0002 per session on Opus 5.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-31.
Other cursor rules, from other repositories
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.