remnawave-nodes

remnawave-nodes is a skill for Codex from JonesPitkin/remnawave-skills. It costs 36 tokens per session (912 once invoked), scanned A, original, MIT.

A deployment guide for Remnawave Node, a lightweight container that runs Xray-core and connects to the Remnawave Panel.

In plain words
What is it for?
Use it to install a node with Docker, connect it to the Panel, assign a configuration profile, and manage node-side firewall and operational tasks.
Why use it?
It explains the setup needed because the Panel alone does not include Xray-core.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to install a node with Docker, connect it to the Panel, assign a configuration profile, and manage node-side firewall and operational tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonespitkin/remnawave-skills/remnawave-nodes
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.

Any agent
npx skills add JonesPitkin/remnawave-skills --skill remnawave-nodes
Clone the repo
git clone --depth 1 https://github.com/JonesPitkin/remnawave-skills

Made for: Codex.

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 remnawave-nodes

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonespitkin/remnawave-skills/remnawave-nodes/github.svg)](https://agentmods.dev/skills/jonespitkin/remnawave-skills/remnawave-nodes)
Your own site
<a href="https://agentmods.dev/skills/jonespitkin/remnawave-skills/remnawave-nodes"><img src="https://agentmods.dev/badge/skills/jonespitkin/remnawave-skills/remnawave-nodes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for remnawave-nodes

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonespitkin/remnawave-skills/remnawave-nodes"><img src="https://agentmods.dev/badge/skills/jonespitkin/remnawave-skills/remnawave-nodes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 912 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00036 $0.00912
Opus 5 $0.00018 $0.00456
Sonnet 5 $0.00007 $0.00182
Haiku 4.5 $0.00004 $0.00091

Measured 12d ago against content hash 0740f94e66ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

remnawave-nodes 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 12d 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.

remnawave-nodes/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Remnawave Nodes

Назначение

Этот skill покрывает deployment и подключение Remnawave Node, node firewall, Config Profile assignment и официально описанные advanced node practices.

Теория

Официальная документация определяет Remnawave Node как lightweight container, который включает Xray-core. Panel itself не включает Xray-core, поэтому полноценная эксплуатация Remnawave требует Node.

Текущий official Nodes guide покрывает не только создание Node, но и operational blocks:

  • hourly statistics cards;
  • Actions block;
  • Consumption;
  • Tracking & Billing;
  • More actions;
  • Node status indicators;
  • Copy Node UUID.

Практика

  1. Убедиться, что на node server установлен Docker.
  2. Создать каталог:
    • mkdir /opt/remnanode && cd /opt/remnanode
  3. В Panel открыть Nodes -> Management и нажать +.
  4. В форме добавить node и обратить внимание на Node Port.
  5. Нажать Copy docker-compose.yml.
  6. Создать локальный docker-compose.yml на node server и вставить туда содержимое.
  7. Запустить:
    • docker compose up -d && docker compose logs -f -t
  8. Вернуться в Panel, нажать Next, выбрать Config Profile и завершить создание.
  9. Ограничить NODE_PORT firewall-правилом только для IP панели.
  10. После создания Node проверить operational card:
  • hourly stats;
  • status icon/background;
  • Xray uptime;
  • traffic usage until refill.
  1. Проверить Actions block:
  • Update
  • Restart all nodes
  1. Проверить Consumption:
  • multiplier/коэффициент меняет способ учета user traffic;
  • 1.0 означает обычный учет;
  • 0.5 и 2.0 меняют биллинг-эквивалент трафика.
  1. Проверить Tracking & Billing:
  • Infrastructure Provider
  • Track traffic usage
  • Traffic limit
  • Reset day
  • Notification %
  1. В More actions проверить:
  • Show usage
  • Copy Node UUID
  • Disable
  • Delete

Типовые сценарии

  • Первое подключение одного Node к Panel.
  • Назначение нового Config Profile на Node.
  • Настройка traffic coefficient для billing semantics.
  • Включение node-side limit tracking с monthly reset.
  • Подключение geosite/geoip mount-ов к Node.
  • Вынос node logs на host filesystem с logrotate.
  • Передача TLS certificate files в Node через Panel workflow.

Read the full file on GitHub · 98 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 98 lines · 36 tokens per session scan A 0740f94e66ef

Subscribe to this mod's changes

remnawave-nodes is a skill published in the GitHub repository JonesPitkin/remnawave-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 912 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

detecting-privilege-escalation-in-kubernetes-pods

Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.

xalgorix/xalgorix · 40 tokens

implementing-rbac-hardening-for-kubernetes

Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.

xalgorix/xalgorix · 41 tokens

docker-socket-mount

Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.

PurpleAILAB/Decepticon · 67 tokens