remote

remote is a command for coding agents from nordbyte/nordrelay. It costs 16 tokens per session (403 once invoked), scanned A, original, MIT.

A command for managing the local NordRelay process, which connects coding-agent sessions to the WebUI and enabled chat services. It can start, stop, restart, inspect, or run the process in the foreground for debugging.

In plain words
What is it for?
Use it to start NordRelay in the background, check or change its state, or run it visibly while troubleshooting.
Why use it?
It gathers common process-management tasks in one place and helps diagnose connection problems without replacing NordRelay’s login-protected control interfaces.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/nordbyte/nordrelay/remote
Clone the repo
git clone --depth 1 https://github.com/nordbyte/nordrelay

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for remote

README.md
[![agentmods](https://agentmods.dev/badge/commands/nordbyte/nordrelay/remote.svg)](https://agentmods.dev/commands/nordbyte/nordrelay/remote)
Your own site
<a href="https://agentmods.dev/commands/nordbyte/nordrelay/remote"><img src="https://agentmods.dev/badge/commands/nordbyte/nordrelay/remote.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 403 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00403
Opus 5 $0.00008 $0.00201
Sonnet 5 $0.00003 $0.00081
Haiku 4.5 $0.00002 $0.00040

Measured 3d ago against content hash b235ef20f844, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

remote scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/nordrelay/commands/remote.md · 39 lines

What it actually says

/nordrelay:remote

Manage the local NordRelay process.

This command is a process-manager shortcut. NordRelay provides full session control through its login-protected WebUI and enabled Telegram, Discord, Slack, and Matrix adapters, including trusted peer-node routing. This Codex command starts, stops, restarts, inspects, or troubleshoots the local runtime; it does not replace those control surfaces.

Codex plugin commands are namespaced by the plugin id in current plugin-aware command surfaces. The unnamespaced /remote command is not available in current Codex TUI builds.

Arguments

  • empty: start the connector in the background
  • status: show connector status
  • stop: stop the connector
  • restart: restart the connector
  • foreground: run the connector in the foreground for debugging

Workflow

  1. Locate the plugin root containing .codex-plugin/plugin.json with "name": "nordrelay". In a source checkout this is usually <repo>/plugins/nordrelay.
  2. Check that the NordRelay env file exists and that the credentials required by the enabled control surfaces are configured. TELEGRAM_BOT_TOKEN is required only when Telegram is enabled. A NordRelay admin user is required before the WebUI or chat adapters can control sessions.
  3. Run the connector command from the plugin root:
node scripts/nordrelay.mjs ${ARGUMENTS:-start}
  1. If ${ARGUMENTS} is empty, use start.
  2. After start or restart, run node scripts/nordrelay.mjs status and report the PID, selected thread id if visible, and log file.
  3. If startup fails because dependencies are missing, run npm install and npm run build in the repository root.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 39 lines · 16 tokens per session scan A b235ef20f844

Subscribe to this mod's changes

remote is a command published in the GitHub repository nordbyte/nordrelay (10 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.