Well I'd like to pass some things to the flake and this is what I came up with:

{
  description = "Custom Flake";

  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-24.11";
    nixpkgs-unstable.url = "github:nixos/nixpkgs/nixos-unstable";
    myvendor-scripts.url = "git+https://git.myvendor.de/linux/scripts";
  };

  outputs = { nixpkgs, nixpkgs-unstable, myvendor-scripts, ... }: let
    getModule = {system, flakefolder}: let
      homeManagerModule = import ./modules {
        lib = nixpkgs.lib;
        pkgs = nixpkgs.legacyPackages.${system};
        pkgs-unstable = nixpkgs-unstable.legacyPackages.${system};
        flakefolder = flakefolder;
        myvendor-scripts = myvendor-scripts;
      };
    in {
      home-manager = homeManagerModule ;
    };
  in {
    getModule = getModule;
  };
}

But this way I have to define everything a module would need - like lib, config, etc. Doesn't seem to be a good solution. Am I missing something?

when you have something like in a "consuming flake"

      homeConfigurations.dram = home-manager.lib.homeManagerConfiguration {
        ...
        modules = [
          foo
          bar
          ./home.nix
        ];
      };

all three modules are on equal footing, they can each have options and config, and any one module can set the values of options defined in any module

when you have something like in a "consuming flake"

      homeConfigurations.dram = home-manager.lib.homeManagerConfiguration {
        ...
        modules = [
          foo
          bar
          ./home.nix
        ];
      };

all three modules are on equal footing, they can each have options and config, and any module can set the values of options defined in any module

you would have something like

{ config, lib, ... }:

{
  options = {
    my-scripts.flakefolder = lib.mkOption {
      type = with lib.types; types.str;
      description = "The flake folder for my-scripts";
    };
  };

  config = {
    home.packages = [
      (something config.my-scripts.flakefolder)
    ];
  };
}

and then in your regular module you would set

  my-scripts.flakefolder = "git+file:///home/whatever/you-get-the-idea";

So that would result in something like this?

  outputs = { nixpkgs, nixpkgs-unstable, myvendor-scripts, ... }: let
    getModule = {system}: let
      homeManagerModule = import ./modules {
        inherit myvendor-scripts;
        pkgs = nixpkgs.legacyPackages.${system};
        pkgs-unstable = nixpkgs-unstable.legacyPackages.${system};
      };
    in {
      home-manager = homeManagerModule ;
    };
  in {
    getModule = getModule;
  };

config and lib can't be used in submodules then.

I have a bunch of eg.

    inputs.patch-arsenik = {
      url = "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch";
      flake = false;
    };

in the flake for my systems, applied with patchedNixpkgs = inputs.nixpkgs.legacyPackages.x86_64-linux.applyPatches { src = inputs.nixpkgs; patches = [ inputs.patch-arsenik ]; };, for some of my PRs I want in my pkgs but are not merged. This allow to have up-to-date patches with low effort.

But recently, github rate limits have been hitting me on like 100% of my nix flake update. Anybody has a workaround ?

I have a bunch of eg.

    inputs.patch-arsenik = {
      url = "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch";
      flake = false;
    };

in the flake for my systems, applied with patchedNixpkgs = inputs.nixpkgs.legacyPackages.x86_64-linux.applyPatches { src = inputs.nixpkgs; patches = [ inputs.patch-arsenik ]; };, for some PRs I want in my pkgs but are not merged. This allow to have up-to-date patches with low effort.

But recently, github rate limits have been hitting me on like 100% of my nix flake update. Anybody has a workaround ?