example-custom-* disabled so installer does not find them when trying to install from npx

example-custom-content/README.md

@@ -2,3 +2,7 @@
 
 This is a demonstration of custom stand along agents and workflows. By having this content all in a folder with a custom.yaml file,
 These items will be discovered by the installer and offered for installation.
+
+This is how you could also create and share other custom agents and workflows not tied to a specific module.
+
+To see how these become installable, rename custom.bak -> custom.yaml and run the installer from the location you also have put this folder.

example-custom-module/mwm/README.md

@@ -2,3 +2,11 @@
 
 This module is an example and is not at all recommended for any usage, this module was not vetted by any medical professionals and should
 be considered at best for entertainment purposes only.
+
+IF you want to see how a custom module installation works, copy this whole folder to where you will be installing from with npx, and rename
+"\_module-installer/install-config.bak" to "\_module-installer/install-config.yaml".
+
+You should see the option in the module selector when installing.
+
+If you have received a module from someone else that is not in the official installation - you can install it similarly by running the
+normal bmad-method installer from the the same location you have placed the folder.