agentmods.dev

node-new

A command that creates the starting files for a new bubbaloop node, which is a component representing a sensor, actuator, processor, or gateway.

In plain words
What is it for?
Use it to scaffold a node in Rust or Python, define its capabilities and commands, validate it, and walk through adding, installing, and starting it.
Why use it?
It guides the initial manifest and command handler setup, helping avoid malformed node definitions and registration errors.

Command

28 2mo ago A scan 30 tokens original Apache-2.0
View the source file kornia/bubbaloop
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/kornia/bubbaloop/node-new
Clone the repo
git clone --depth 1 https://github.com/kornia/bubbaloop
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 298 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.00030 $0.00298
Opus 5 $0.00015 $0.00149
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured yesterday against content hash 5489da959eb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

node-new 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 yesterday.

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.

bubbaloop-mcp/commands/node-new.md · 19 lines

What it actually says

Dispatch the bubbaloop-node-author subagent to scaffold a new node named $ARGUMENTS.

The subagent will:

  1. Confirm intended role (sensor / actuator / processor / gateway) and language (rust default, python alternative).
  2. Run bubbaloop node init <name> --type <lang> to create the directory tree.
  3. Walk through the manifest (node.yaml) shape — capabilities, commands, topics, hardware requirements.
  4. Show the command queryable handler skeleton that correctly parses the {command, params} wire envelope (the most common new-node footgun — see node-author guide).
  5. Recommend the verb_noun command-naming convention (matches OBS MCP server, improves small-model accuracy by 13–15%).
  6. Run bubbaloop node validate to confirm the manifest is well-formed.
  7. Walk through bubbaloop node add → bubbaloop node install → node_start via MCP to test end-to-end.

If you already have an in-progress node directory, point that out — the subagent can adapt to existing layouts rather than scaffolding from scratch.

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. yesterday First seen · 19 lines · 30 tokens per session scan A 5489da959eb0

Subscribe to this mod's changes

node-new is a command published in the GitHub repository kornia/bubbaloop (28 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 298 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-30.

Building agentsFrontendLanguagesai-agentcomputer-visionedge-airoboticsrustvlm
Related

Other commands, from other repositories

vios-api

Query VIOS (VST) REST APIs: sensor list, recording timelines, video clip extraction, snapshot capture, add/delete sensors and streams.

NVIDIA-AI-Blueprints/video-search-and-summarization · 32 tokens

rebase

Data-preserving git rebase and conflict resolution onto v2.1 (or any target branch).

NVIDIA-AI-Blueprints/video-search-and-summarization · 23 tokens

vios-architecture

Explain the VIOS stream-processor and sensor microservice deployment architecture: containers, ingress, RTSP, file-upload, WebRTC, Envoy, SDR, routing, and event flow.

NVIDIA-AI-Blueprints/video-search-and-summarization · 42 tokens

vios-git

VIOS git conventions: branch names, commit messages, and merge-request descriptions. Use before creating any branch, commit, or MR.

NVIDIA-AI-Blueprints/video-search-and-summarization · 32 tokens

vst-ui-dev

This skill should be used when the user asks to "add a feature", "fix a bug", "create a component", "implement UI", "update the VST UI", "change the dashboard", "modify the video player", or any other development task on the VST web client (vst-ui-ts TypeScript/React codebase). Covers the full development loop: plan →…

NVIDIA-AI-Blueprints/video-search-and-summarization · 0 tokens

ui-test

Run VIOS UI tests using the playwright plugin.

NVIDIA-AI-Blueprints/video-search-and-summarization · 12 tokens