Nodus
GitHub Install

Paste a package source. Get the command.

Use GitHub shorthand, a repo URL, a full Git URL, or a local path. Nodus can also pin a tag, branch, version, or revision and narrow the install to specific components.

Generate a real nodus add command.

Start with the package source, then add pinning, adapters, components, or install behavior only when you need them.

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

Switch between project and global installs, record dev-only dependencies, or preview changes first.

Install options

Build the exact install shape you need.

The CLI supports more than a bare source. The page should expose the options people actually use without collapsing everything into dense controls.

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 --global, --dev, --sync-on-launch, and --dry-run to match the exact install workflow you need.