nodel-use

nodel-use is a skill for Claude Code, Codex from scroix/nodel-skills. It costs 70 tokens per session (673 once invoked), scanned A, original, MIT.

A tool for inspecting and controlling running Nodel hosts and their nodes through a REST API. Nodel is a platform for running connected software components called nodes.

In plain words
What is it for?
Use it to read status, console logs, events, parameters, actions, bindings, scripts, and files, or to restart, rename, configure, and remove nodes.
Why use it?
It helps you check live state and logs, diagnose problems, and make targeted changes without manually using the Nodel interface.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the nodel plugin — 4 skills shipped together

Good fit Use it to read status, console logs, events, parameters, actions, bindings, scripts, and files, or to restart, rename, configure, and remove nodes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/scroix/nodel-skills/nodel-use
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 scroix/nodel-skills --skill nodel-use
Clone the repo
git clone --depth 1 https://github.com/scroix/nodel-skills

Made for: Claude Code, Codex.

Or install nodel, the plugin that ships this one along with the rest of its 4 skills.

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 nodel-use

README.md
[![agentmods](https://agentmods.dev/badge/skills/scroix/nodel-skills/nodel-use/github.svg)](https://agentmods.dev/skills/scroix/nodel-skills/nodel-use)
Your own site
<a href="https://agentmods.dev/skills/scroix/nodel-skills/nodel-use"><img src="https://agentmods.dev/badge/skills/scroix/nodel-skills/nodel-use/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 nodel-use

Your own site · 80×15
<a href="https://agentmods.dev/skills/scroix/nodel-skills/nodel-use"><img src="https://agentmods.dev/badge/skills/scroix/nodel-skills/nodel-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 673 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00070 $0.00673
Opus 5 $0.00035 $0.00336
Sonnet 5 $0.00014 $0.00135
Haiku 4.5 $0.00007 $0.00067

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

Security

Grade A, and why

nodel-use scanned grade A with 1 finding 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 11d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl http://localhost:8085/REST/nodes
skills/nodel-use/SKILL.md · 64 lines

How it starts

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

Interacting with Running Nodel Instances

Inspect and manage live Nodel hosts through their REST API.

Workflow

  1. Identify the correct host and port. With no configured port, Nodel reuses its cached last port or falls back to 8085.
  2. List nodes and confirm the exact target name before using a node-scoped endpoint.
  3. Read console, activity, parameters, actions, and events before mutating state.
  4. Test the narrowest safe action or diagnostic call, then re-read logs and state.
  5. Use restart, rename, deletion, script, parameter, binding, or file writes only when the requested change requires them.

Quick Start

URL-encode node names in paths (My Node becomes My%20Node).

# List local nodes
curl http://localhost:8085/REST/nodes

# Read recent console entries
curl "http://localhost:8085/REST/nodes/My%20Node/console?from=0&max=50"

# Invoke a string action
curl -X POST "http://localhost:8085/REST/nodes/My%20Node/actions/Power/call" \
  -H "Content-Type: application/json" \
  -d '{"arg":"On"}'

Safety and Response Rules

  • Inspect an action's metadata before choosing its argument shape.
  • Send JSON to service endpoints, including {} when a POST has no explicit payload.
  • Treat /files/save as the raw-file-content exception.
  • Use the previous ISO started timestamp with hasRestarted when waiting for a restart.
  • Require confirm=true for node removal and confirm the target name immediately beforehand.
  • Add ?trace only when diagnosing serialization, Python, or unexpected server errors; routing and not-found failures deliberately omit stack traces.
  • Preserve unrelated nodes, parameters, bindings, scripts, and files.

Debugging Order

  1. Confirm the node exists and inspect discovery when remote visibility matters.
  2. Read console for startup or protocol errors.
  3. Read action/event activity and current parameters.
  4. Inspect action and event metadata before invoking or evaluating anything.
  5. Use eval for a narrow expression and exec only for deliberate diagnostic code.
  6. Re-read the console after every active test.

Read the full file on GitHub · 64 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. 11d ago First seen · 64 lines · 70 tokens per session scan A d8209ad3c703

Subscribe to this mod's changes

nodel-use is a skill published in the GitHub repository scroix/nodel-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 673 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens