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/status)<a href="https://agentmods.dev/commands/kornia/bubbaloop/status"><img src="https://agentmods.dev/badge/commands/kornia/bubbaloop/status/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/status"><img src="https://agentmods.dev/badge/commands/kornia/bubbaloop/status.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.00010 | $0.00141 |
| Opus 5.5 | $0.00004 | $0.00056 |
| Sonnet 5.5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
status 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
Use the bubbaloop MCP server.
- Call
system_statusfor a top-line view (machine_id, node counts, daemon health). - Call
node_listfor the per-node breakdown.
Render the result as a single compact table with columns: name, status, health, type, installed, built.
If any node reports Failed or Unhealthy:
- Call
node_logs(node_name=...)for that node only - Surface the last error line beneath the table
Keep the response under one screen. No narration of intermediate calls.
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 · 17 lines · 10 tokens per session scan A 0a988a6a20df
status is a command published in the GitHub repository kornia/bubbaloop (29 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 141 once invoked, about $0.0000 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.