The terminal edition of Darknode — a single command that drives a full security toolkit and hosts Nexus, the AI coding agent. Recon, exploitation helpers, practice labs, governance, and an autonomous AI layer, all from your shell.
You (a command)
|
v
darknode.js (dispatch + first-run setup)
|
+--> nexus ------> Nexus engine (lib/nexus) ---> Ollama (local) | Claude / API (cloud)
| plan -> act -> observe, cost meter, /undo
|
+--> toolkit ----> external tools: nmap · sqlmap · nuclei · ffuf · httpx ...
|
+--> governance -> identity · usage ledger · compliance bundle
|
+--> lab --------> docker practice targets (spin up / tear down)
v
Results in your terminal
Most subcommands run through the toolkit or governance layers; nexus (aliases
code, ai) hands the turn to the AI engine, which edits files and runs commands
against your workspace with a live token/cost readout.
darknode-cli/
├── darknode.js # entry point + command dispatch
├── lib/
│ ├── cli/ # command implementations & shared CLI helpers
│ ├── nexus/ # the Nexus AI-coder engine
│ ├── governance/ # identity, usage ledger, compliance/policy
│ └── toolkit/ # external-tool drivers (recon / web / passwords / ...)
├── scripts/ # build & release helpers
├── test/ # test suite (npm test)
├── docs/ # command reference & guides
│ └── NEXUS.md # complete Nexus guide (every command explained)
├── package.json
└── README.md
Requires Node 18 or newer.
git clone https://github.com/Darknode-Official/darknode-cli
cd darknode-cli && npm install
node darknode.js
# optional: put the `darknode` and `nexus` commands on your PATH
npm install -g .Free to download and use (see LICENSE).
darknode nexus # the AI coding agent (interactive TUI)
darknode nexus "fix auth" # one-shot task
darknode nexus --engine ollama # local, private models
darknode <tool> ... # drive the security toolkit
darknode mcp # MCP server: the Darknode Deck's tools for any AIdarknode mcp is an MCP server (stdio) that gives any MCP client the Darknode
Deck's analysis tools: Infrastructure as Code, Kubernetes, firewall configs,
cloud audit logs, sign-ins, scanner imports and the rest. The engines are the
Deck's own, downloaded from darknode.ai and run on your machine, so the files
an AI hands them stay local. Which tools are listed follows your Darknode plan
(sign in with darknode nexus, then /login).
claude mcp add darknode -- node /path/to/darknode-cli/darknode.js mcp # Claude Code
codex mcp add darknode -- node /path/to/darknode-cli/darknode.js mcp # Codex CLI
gemini mcp add darknode node /path/to/darknode-cli/darknode.js mcp # Gemini CLIClaude Desktop, Cursor and other clients take the same command in their
mcpServers config: {"command": "node", "args": ["/path/to/darknode-cli/darknode.js", "mcp"]}.
To send results to your Deck, set DARKNODE_API_KEY (a workspace key with the
ingest:write scope, from Deck > API & Ingest) and DARKNODE_WORKSPACE.
See docs/NEXUS.md for the complete Nexus guide — every command, feature, and configuration option explained.
npm test| Engine | Models | Cost |
|---|---|---|
| Claude | opus, sonnet, haiku, fable | Subscription or API |
| Gemini | gemini-2.5-pro, flash | API |
| Codex | gpt-5-codex, o4-mini | API |
| OpenCode | any configured provider | API |
| Aider | any configured model | API |
| Ollama | any local model | Free |
- 6 AI engines behind one interface
- Cost saving:
/cowork,/lean,/cheap,/budget,/estimate - Multi-engine:
/race,/ensemble,/bench - Code tools:
/agents,/plan,/review,/commit,/undo - Security:
/guard,/redact,/secrets,/policy,/audit - Customizable:
.nexus/NEXUS.md, custom commands, styles, hooks, MCP servers
The CLI can run external tools and, via Nexus, edit files and run commands. Use it
only against systems you're authorized to test, and prefer the local ollama engine
for sensitive code. Credentials are never stored in source.
Users bring their own AI API keys. No AI runs on Darknode servers.
See LICENSE.