nodus
Health Warn
- License — License: Apache-2.0
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Fail
- rm -rf — Recursive force deletion command in install.sh
Permissions Pass
- Permissions — No dangerous permissions requested
This tool is a package manager for AI agent tooling. It installs agent packages, skills, and rules from GitHub or local paths into your repository, and writes the necessary adapter configuration files.
Security Assessment
Overall Risk: Medium. As a package manager, this tool naturally executes shell commands and makes outbound network requests to fetch external dependencies from GitHub and its own servers. The automated audit failed because the web-based install script (`install.sh`) contains a `rm -rf` recursive force deletion command, which is a common risk for unintended data loss if the script fails or is manipulated. Additionally, it offers a feature where AI assistants can fetch operational instructions directly from a remote URL. While no hardcoded secrets were found and no explicitly dangerous permissions are requested, piping web scripts to bash and downloading external code always carries inherent risks that require manual review.
Quality Assessment
The project is actively maintained, with its most recent push happening today. It is properly licensed under the permissive Apache-2.0 license. However, community trust and visibility are currently very low. With only 5 GitHub stars, the project is extremely new, meaning it has not yet been battle-tested or widely vetted by a larger developer community.
Verdict
Use with caution. While the underlying Rust project is open and active, the low community adoption and the presence of recursive deletion in the installer script mean you should review the shell script before executing it.
Install skills, agents, rules, and commands from GitHub or a local path, lock the exact version, and write the runtime files your repo actually uses.
Nodus
Add agent packages to your repo with one command.
Nodus installs agent packages from GitHub, Git URLs, or local paths, locks the exact revision, and writes only the adapter runtime files your repo actually uses.
English • 简体中文
Install • For AI Assistants • Quick Start • CLI Help • Learn More • Contributing
What Is Nodus?
Nodus is a package manager for repo-scoped agent tooling.
If a package publishes content such as skills/, agents/, rules/, or commands/, Nodus can:
- add it from GitHub, Git, or a local path
- record what you asked for in
nodus.toml - lock the exact resolved revision in
nodus.lock - write managed files into adapter roots such as
.codex/,.claude/,.cursor/,.github/,.agents/, or.opencode/ - compose managed MCP server config for supported runtimes, including
.mcp.json,.codex/config.toml, andopencode.json - prune stale generated files without touching unmanaged ones
For most teams, the normal flow is:
nodus add <package> --adapter <adapter>
nodus doctor
Install
Install from crates.io:
cargo install nodus
Install the latest prebuilt binary on macOS or Linux:
curl -fsSL https://nodus.elata.ai/install.sh | bash
Install with Homebrew:
brew install nodus-rs/nodus/nodus
Install the latest prebuilt binary on Windows with PowerShell:
irm https://nodus.elata.ai/install.ps1 | iex
Windows install command failed?
If the command fails, install PowerShell 7, restart your terminal, then run:
winget install --id Microsoft.PowerShell --source winget
pwsh -NoProfile -Command "irm https://nodus.elata.ai/install.ps1 | iex"
For AI Assistants
If you want an AI assistant to operate Nodus for you, give it the fetchable prompt URL:
That prompt gives the assistant concrete Nodus operating instructions, helps it choose the right nodus add command, and still ends with nodus doctor.
Quick Start
Install a package into the current repo and verify the result:
nodus add nodus-rs/nodus --adapter codex
nodus doctor
That flow:
- creates
nodus.tomlif the repo does not have one yet - records the dependency in
nodus.toml - resolves and locks the exact revision in
nodus.lock - writes the managed runtime files for the selected or detected adapter
If the package publishes mcp_servers, Nodus now carries that MCP config into the repo's managed
runtime outputs as well. Today that includes the legacy project .mcp.json, Codex.codex/config.toml, and OpenCode opencode.json.
If the package is a wrapper that exposes multiple child packages, nodus add now records the
wrapper itself and leaves child packages disabled until you either edit members innodus.toml or opt in up front with --accept-all-dependencies.
If you want a user-level install instead of repo-scoped state, use --global explicitly:
nodus add nodus-rs/nodus --global --adapter codex
CLI Help
nodus --help is the main command guide.
Start there when you want to learn the workflow, then open command-specific help as needed:
nodus --help
nodus add --help
nodus sync --help
nodus doctor --help
Commands most users need:
nodus add <package> --adapter <adapter>to install a package into the current reponodus info <package-or-alias>to inspect a package before or after installnodus syncto rebuild managed outputs from the versions already recordednodus updateto move dependencies to newer allowed revisionsnodus remove <alias>to remove a dependency and prune what it ownednodus cleanto clear shared repository, checkout, and snapshot cache data without changing project manifests or managed outputsnodus doctorto check that the repo, lockfile, shared store, and managed outputs still agree
Learn More
- Docs: https://nodus.elata.ai/docs/
- Install guide: https://nodus.elata.ai/install/
- Package command generator: https://nodus.elata.ai/packages/
- Consumer manifest example: examples/nodus.toml
- Package author manifest example: examples/package-author.nodus.toml
For package authoring details, workspace packaging, managed exports, or relay workflows, prefer the website docs and nodus --help over treating this README as the full command reference.
That applies to MCP packages too: package authors can publish mcp_servers in nodus.toml, and
consumers get the matching managed project config for the adapter they use.
Contributing
See CONTRIBUTING.md for local development and release checks.
License
Licensed under Apache-2.0.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found