Paste a package source. Get the command.

Use GitHub shorthand, a repo URL, a full Git URL, or a local path. Start with `nodus add <source> --adapter <adapter>` for project-scoped installs, then add pinning or other options only when you need them.

Generate a real nodus add command.

Start with a package source, then add adapter selection, pinning, or install behavior only when you need it.

GitHub links normalize to owner/repo. Local paths and generic Git URLs stay unchanged.

Pinning

Leave this empty to use the latest tag or the default branch fallback.

Adapters

Add one or more adapters only when repo auto-detection is not enough.

Adapters (optional)

Components

Narrow the install only if you want part of a package instead of the whole package.

Components (optional)

Scope and behavior

Project-scoped install is the default. Supported adapters also persist startup sync hooks by default. Switch to global only when you need home-scoped outputs, or opt out of hooks before you run the command.

Install options

Build the exact install shape you need.

The CLI supports more than a bare source. The page surfaces the options people actually use while keeping the project-scoped default visible.

Pin a release or development ref

Use --tag, --branch, --version, or --revision when the default latest-tag behavior is not what you want.

Narrow to specific package components

Repeat --component to install only skills, agents, rules, or commands.

Switch scope or preview the result

Use --dev, --no-sync-on-launch, and --dry-run to match the exact install workflow you need. Use --global only when you want home-scoped outputs.