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.
git clone --depth 1 https://github.com/kornia/bubbaloopWrote 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.
[](https://agentmods.dev/commands/kornia/bubbaloop/node-new)<a href="https://agentmods.dev/commands/kornia/bubbaloop/node-new"><img src="https://agentmods.dev/badge/commands/kornia/bubbaloop/node-new/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.
<a href="https://agentmods.dev/commands/kornia/bubbaloop/node-new"><img src="https://agentmods.dev/badge/commands/kornia/bubbaloop/node-new.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.00298 |
| Opus 5.5 | $0.00012 | $0.00119 |
| Sonnet 5.5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 1mo 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.
What it actually says
Dispatch the bubbaloop-node-author subagent to scaffold a new node named $ARGUMENTS.
The subagent will:
- Confirm intended role (sensor / actuator / processor / gateway) and language (rust default, python alternative).
- Run
bubbaloop node init <name> --type <lang>to create the directory tree. - Walk through the manifest (
node.yaml) shape — capabilities, commands, topics, hardware requirements. - Show the command queryable handler skeleton that correctly parses the
{command, params}wire envelope (the most common new-node footgun — see node-author guide). - Recommend the
verb_nouncommand-naming convention (matches OBS MCP server, improves small-model accuracy by 13–15%). - Run
bubbaloop node validateto confirm the manifest is well-formed. - Walk through
bubbaloop node add→bubbaloop node install→node_startvia 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.
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.
- 1mo ago First seen · 19 lines · 30 tokens per session scan A 5489da959eb0
node-new is a command published in the GitHub repository kornia/bubbaloop (29 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 298 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
rebase
Data-preserving git rebase and conflict resolution onto v2.1 (or any target branch).
vios-architecture
Explain the VIOS stream-processor and sensor microservice deployment architecture: containers, ingress, RTSP, file-upload, WebRTC, Envoy, SDR, routing, and event flow.
vios-git
VIOS git conventions: branch names, commit messages, and merge-request descriptions. Use before creating any branch, commit, or MR.
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 →…
vios-dev-sanity
Execute VIOS/VST sanity test cases from the viosdevsanity.xlsx spreadsheet against a running VIOS web UI instance using Playwright. Tests are loaded dynamically from the xlsx — no hardcoded test matrix.
ui-dev-server
Configure backend IP in config.tsx, install deps, and start the UI dev server.