Setup

Connect your agent

Install Nipmod, connect your agent and ask it to search the archive before package installs.

Install once Choose agent MCP details Codex and Claude

Step 1

Install Nipmod once

Paste this in Terminal. After it finishes, run the check command below it.

curl -fsSLO https://nipmod.com/install.sh && bash install.sh

nipmod doctor --online

nipmod setup agents --include-codex --include-hermes

Open Terminal

Use the macOS Terminal app, your editor terminal or the terminal inside your agent tool.

Install once

Paste the install command. It puts the Nipmod CLI on the machine.

Connect agent

Pick Codex, Claude Code, OpenCode or Hermes and paste the matching setup command.

Paste prompt

Start a new agent chat and tell it to use Nipmod before package installs.

Step 2

Choose your agent

Paste one matching command. This gives the agent direct Nipmod tools for package search, trust checks and install plans.

Codex

Codex desktop and CLI

Registers Nipmod as a local MCP server through the Codex CLI.

nipmod setup codex

Check

codex mcp list

Claude Code

Project scoped MCP

Writes the project .mcp.json file and preserves other MCP servers.

nipmod setup claude

Check

claude mcp list

OpenCode

Local opencode.json

Writes opencode.json with the local Nipmod MCP server.

nipmod setup opencode

Check

opencode mcp list

Hermes

Global Hermes MCP config

Adds Nipmod under mcp_servers in ~/.hermes/config.yaml.

nipmod setup hermes

Check

hermes chat, then /reload-mcp

Step 3

Tell the agent

Start a new chat after setup and paste this once.

Use Nipmod before package installs.

Use Nipmod before installing agent packages. Read https://nipmod.com/llms.txt and https://nipmod.com/.well-known/nipmod.json. Search the Nipmod archive first, view exact metadata, inspect trust, create an install plan, ask before writing files, then audit and export SBOM.

Find packages

Your agent can search the public Nipmod registry.

Inspect trust

It can read source, claim proof, permissions, signatures and audit evidence before using code.

Plan installs

It can prepare an install plan and ask before any workspace lockfile write.

Result

What changes after setup

No Nipmod account required

Search, inspect, plan and audit are usable from the public registry.

Agent archive access

After MCP is connected, the agent can call Nipmod tools instead of guessing package names from chat memory.

Controlled writes

The install tool writes only after the agent has a plan and explicit write-lockfile approval.