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/doctor)<a href="https://agentmods.dev/commands/kornia/bubbaloop/doctor"><img src="https://agentmods.dev/badge/commands/kornia/bubbaloop/doctor/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/doctor"><img src="https://agentmods.dev/badge/commands/kornia/bubbaloop/doctor.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.00038 | $0.00643 |
| Opus 5.5 | $0.00015 | $0.00257 |
| Sonnet 5.5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
doctor 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
Run a comprehensive bubbaloop install check. Use the bubbaloop MCP server where the check is in-band; fall back to Bash for things outside the daemon (env vars, Zenoh router process).
For each check below, output ONE line in this exact format:
✓ <check> OR
✗ <check> — <one-line fix command>
Sequence (each depends on the previous succeeding):
BUBBALOOP_MCP_TOKENenv var — present, non-empty, length plausible (≥ 16 chars). Fix:export BUBBALOOP_MCP_TOKEN="$(cat ~/.bubbaloop/mcp-token)"- Token file —
~/.bubbaloop/mcp-tokenexists and is mode 0600. Fix:bubbaloop daemon runonce to regenerate. - Zenoh router — port 7447 listening (check via
ss -tlnp 2>/dev/null | grep -q :7447). Fix:~/.bubbaloop/bin/zenohd > /tmp/zenohd.log 2>&1 & - Bubbaloop daemon — port 8088 listening. Fix:
bubbaloop daemon run > /tmp/bubbaloop_daemon.log 2>&1 & - MCP
system_status— call returns success. Verifies the entire transport+auth path. Fix path depends on error: 401 → re-export token, connection refused → step 4, anything else → tail/tmp/bubbaloop_daemon.log. - Tool surface —
tools/listreturns ≥ 40 tools, names usenoun_verb(node_listnotlist_nodes). If old names → daemon is running a pre-rename binary; rebuildcargo build --bin bubbaloopand restart. node_list— call returns ≥ 1 node.- Failed nodes — count of nodes with status
Failed. Surface their names. Fix recommendation:/bubbaloop:diagnose <name>for the first one. - NotInstalled nodes — count + names. Fix:
bubbaloop node install <name>(NOT the MCPnode_installtool — see alignment-notes #11). - Mode — read
BUBBALOOP_MCP_MODEenv var (or note it's unset → admin default). Flag if it'sreadonlyorsafeso the user knows why some tools may be ceiling-restricted.
End with a single-line summary: <n> passed, <m> failed.
If any check fails, follow it with the exact → next: fix command on its own line. Don't narrate intermediate calls. Keep the response under one screen.
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 · 30 lines · 38 tokens per session scan A ad03e28dfd03
doctor is a command published in the GitHub repository kornia/bubbaloop (29 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 643 once invoked, about $0.0002 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.