Nebula mods for Among Us are ordinary BepInEx IL2CPP plugins. The difference is only in how they reach players and how they load. For what Nebula does with a mod in general, see How Nebula delivers mods.
A Nebula mod is a normal BepInEx 6 (IL2CPP) plugin: a .NET 6 class library with a [BepInPlugin] plugin class. Build it as you would any Among Us mod (Reactor / MiraAPI). You upload the compiled .dll; Nebula encrypts it, scans it for malware and delivers it to whitelisted players. You never hand the file out yourself. Reference Reactor and MiraAPI as usual, and depend on them the normal way:
[BepInPlugin("com.you.mymod", "My Mod", "1.0.0")]
[BepInDependency(Reactor.ReactorPlugin.Id)]
[BepInDependency(MiraAPI.MiraApiPlugin.Id)]
public class Plugin : BasePlugin { /* ... */ }
Upload the .dll on the Mods page (global, a server's own, libraries, or optional add-ons). Every upload is malware-scanned; a flagged mod cannot go live until an admin reviews it. Uploading the same name with a new version keeps both: players get whichever version you enable. The mod's name and version are read from its [BepInPlugin] attribute.
Add a hard dependency on the Nebula in-game plugin. Nebula installs that plugin every time it launches the game, so your mod loads normally through Nebula. A copy of the .dll dropped into someone's own BepInEx (which does not have Nebula) is skipped by the game and will not run. Mods that leave this out still work everywhere.
[BepInDependency("com.nebula.bridge", BepInDependency.DependencyFlags.HardDependency)]
Nebula detects this on upload and shows a Secure badge. This is a load-time gate, not encryption: someone who edits the .dll can remove it, but it stops casual copy-and-drop reuse.
Go a step further: opt in to Nebula's in-memory loader and your mod is never written to disk as a .dll. Nebula streams its bytes from the launcher into the game over a live, encrypted session on a private pipe (AES-256-GCM under a fresh key each launch, the key passed in the game's environment, never on disk), and the in-game plugin loads it from memory. Add this one assembly-level marker (no extra reference needed):
[assembly: System.Reflection.AssemblyMetadata("Nebula.InMemory", "1")]
Nebula detects the marker and shows a Secure+ badge (it supersedes Secure, since a memory-loaded mod is inherently Nebula-only). Memory loading is on by default for Secure+ mods, but it is the mod's owner, never the player, who can turn it off: an admin for global mods, a server owner for their server's mods. When it is off, or on an older launcher, the mod still loads, staged like any other mod.
Frameworks can be Secure+ too: the in-memory loader runs after every normal plugin (Reactor, MiraAPI) has loaded and loads Secure+ mods in dependency order, so a framework like CyberAPI loads before the mods that need it. Make sure every mod that depends on your framework is also Secure+ (a plain disk mod would look for it too early and fail).
Each mod has a Storage setting (Memory / SSD / Auto). Memory means the mod can be loaded straight from RAM through BepInEx exactly like a normal plugin, so Reactor and MiraAPI register it as usual, and no .dll is ever written. That happens for Secure+ mods when the mod's owner has memory loading on. Anything else is a file on disk for the session, removed when the game closes (Windows will not let a loaded DLL be deleted any sooner). Auto is the default and picks Memory unless the mod needs a real file.
A mod needs SSD if it reads its own file at runtime: Assembly.Location, CodeBase, or opening a file next to its own .dll. Nebula detects this automatically and recommends SSD. If your mod ships extra files beside itself, keep it on SSD, or use BepInEx's Paths instead.
Libraries (Reactor, MiraAPI, your own framework) go in the Libraries list and are delivered with the mods that need them. CyberAPI is Nebula's pathfinding and navigation framework for Among Us mods; it is only for servers that were granted CyberAPI, so do not depend on it from a mod for a server that was not.