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.
npx agentmods add commands/kornia/bubbaloop/diagnosegit clone --depth 1 https://github.com/kornia/bubbaloopWhat 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 | $0.00013 | $0.00201 |
| Opus 5 | $0.00006 | $0.00101 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
diagnose 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 2d 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
Diagnose node $ARGUMENTS using the bubbaloop MCP server:
node_health(node_name="$ARGUMENTS")— current state, uptime, last heartbeatnode_manifest(node_name="$ARGUMENTS")— declared capabilities, topics, commandsnode_logs(node_name="$ARGUMENTS")— last 50 lines
Decision rules:
- Status not Running → cite the failure cause from logs and suggest
node_start(ornode_buildifis_built=false). - Running but Degraded/Unhealthy → call
node_stream_infoand check whether the data plane is firing; cross-reference recent log lines. - Running and Healthy → confirm and stop; no action needed.
End with a one-line recommendation labelled → action:.
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.
- 2d ago First seen · 19 lines · 13 tokens per session scan A 4cef0f4b75e9
diagnose is a command published in the GitHub repository kornia/bubbaloop (28 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 201 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-30.
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.
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 →…
ui-test
Run VIOS UI tests using the playwright plugin.