Agent skill

Borg Live Debug

Live Borg debugging by exec-ing into the borg-web-ui Docker container.

AGPL-3.0Auto-check: notesDevOps & Cloud

Install Borg Live Debug

skills CLI

$ npx skills add karanhudia/borg-ui --skill borg-live-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install karanhudia/borg-ui borg-live-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/borg-live-debug .claude/skills/borg-live-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "borg-live-debug" agent skill from https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug into .claude/skills/borg-live-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "borg-live-debug", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add karanhudia/borg-ui --skill borg-live-debug -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install karanhudia/borg-ui borg-live-debug --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/borg-live-debug .agents/skills/borg-live-debug && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "borg-live-debug" agent skill from https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug into .agents/skills/borg-live-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "borg-live-debug", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add karanhudia/borg-ui --skill borg-live-debug -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install karanhudia/borg-ui borg-live-debug --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/borg-live-debug .cursor/skills/borg-live-debug && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "borg-live-debug" agent skill from https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug into .cursor/skills/borg-live-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "borg-live-debug", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/karanhudia/borg-ui.git --path .claude/skills/borg-live-debug

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add karanhudia/borg-ui --skill borg-live-debug -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install karanhudia/borg-ui borg-live-debug --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/borg-live-debug .gemini/skills/borg-live-debug && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "borg-live-debug" agent skill from https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug into .gemini/skills/borg-live-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "borg-live-debug", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install karanhudia/borg-ui borg-live-debug

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add karanhudia/borg-ui --skill borg-live-debug -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/borg-live-debug .github/skills/borg-live-debug && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "borg-live-debug" agent skill from https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug into .github/skills/borg-live-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "borg-live-debug", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add karanhudia/borg-ui --skill borg-live-debug -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install karanhudia/borg-ui borg-live-debug --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/karanhudia/borg-ui.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/borg-live-debug .opencode/skills/borg-live-debug && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "borg-live-debug" agent skill from https://github.com/karanhudia/borg-ui/tree/main/.claude/skills/borg-live-debug into .opencode/skills/borg-live-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "borg-live-debug", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: borg-live-debug
GitHub stars: 1.7k
Token cost: ~1.4k tokens
SKILL.md length: 457 words
Files: 1
Skills in repo: 5
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Live Borg debugging by exec-ing into the borg-web-ui Docker container.

Works in 4 steps: Verify the container is running → Probe the environment → Run the borg command and capture output → …
Debugging borg commands
SKILL.md covers Container Details, How to exec into the container, Workflow and Common borg2 command cheat…, plus 5 more sections
Calls docker and python3

What it does

Borg Live Debug is an agent skill from karanhudia/borg-ui. Live Borg debugging by exec-ing into the borg-web-ui Docker container. Use when debugging borg commands, writing tests against real borg output, developing borg 2.0 features, or verifying borg behavior before writing code.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Frontend development, Debugging and Containers. It works with Docker. The repository describes itself as: Replace complex Borg Backup terminal commands with a beautiful web UI. Create, schedule, and restore backups with just a few clicks. The licence is AGPL-3.0.

When your agent uses it

Debugging borg commands
Writing tests against real borg output
Developing borg 2.0 features
Verifying borg behavior before writing code

Example prompts

“/borg-live-debug”

Requirements

Python 3
Docker
Pre-approved tools (allowed-tools): Bash, Read, Edit, Write, Grep, Glob

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Verify the container is running
Probe the environment
Run the borg command and capture output
Use output to write code

What it can do on your machine

Read from SKILL.md and the folder at commit 196a74a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Edit
- Write
- Grep
- Glob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- docker
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Borg Live Debug loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 457 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~60
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read, Edit, Write, Grep, Glob
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from karanhudia/borg-ui at commit 196a74a, republished under its AGPL-3.0 licence (© karanhudia). 457 words, ~1,429 tokens.

Download SKILL.mdSave it as .claude/skills/borg-live-debug/SKILL.md (or your agent's skills folder).

name: borg-live-debug
description: Live Borg debugging by exec-ing into the borg-web-ui Docker container. Use when debugging borg commands, writing tests against real borg output, developing borg 2.0 features, or verifying borg behavior before writing code.
allowed-tools: Bash, Read, Edit, Write, Grep, Glob

Borg Live Debug Skill

You have direct access to a running borg-web-ui Docker container. Use this to run real borg/borg2 commands, inspect actual output, and use that ground truth to write code, tests, and fixes.

Container Details

Container name: borg-web-ui
Borg 1 binary: borg (e.g. /usr/bin/borg or via PATH)
Borg 2 binary: borg2 (e.g. /usr/local/bin/borg2)
Working dir: /app
Data dir: /data (database, SSH keys, repos)
Working user for borg ops: borg (use gosu borg or su borg -c)

How to exec into the container

Run commands inside the container using:

bash

docker exec -it borg-web-ui <command>
# or as the borg user:
docker exec -u borg borg-web-ui <command>
# or for multi-step shell sessions:
docker exec borg-web-ui bash -c "<cmd1> && <cmd2>"

Workflow

When the user asks to debug, test, or develop borg functionality:

Step 1 — Verify the container is running

bash

docker ps --filter name=borg-web-ui --format "{{.Names}} {{.Status}}"

If it's not running, tell the user to start it: docker compose up -d

Step 2 — Probe the environment

bash

# Check borg versions available
docker exec borg-web-ui bash -c "borg --version 2>/dev/null; borg2 --version 2>/dev/null"

# Check what repos are configured (from DB or env)
docker exec borg-web-ui bash -c "ls /data/ 2>/dev/null"

Step 3 — Run the borg command and capture output

Run the exact borg command you need to test. Always capture both stdout and stderr:

bash

docker exec -u borg borg-web-ui bash -c "BORG_PASSPHRASE='' borg list /path/to/repo 2>&1"
# For borg2:
docker exec -u borg borg-web-ui bash -c "BORG_PASSPHRASE='' borg2 rinfo /path/to/repo 2>&1"

Key environment variables to set when running borg commands:

BORG_PASSPHRASE — passphrase (empty string if unencrypted)
BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=yes — skip prompts for unencrypted repos
BORG_RSH — custom SSH command if needed
BORG_REMOTE_PATH — path to borg on remote (for SSH repos)

Step 4 — Use output to write code

After seeing the real output:

Parse the exact JSON structure (use borg ... --json wherever possible)
Match error messages exactly for error handling
Match field names precisely in Python code
Write tests using real fixture data from the output

Show full SKILL.md (224 more words)Show less

Common borg2 command cheat sheet (key differences from borg1)

Task	Borg 1	Borg 2
Init repo	`borg init REPO`	`borg2 rcreate REPO`
Repo info	`borg info REPO`	`borg2 rinfo REPO`
Delete repo	`borg delete REPO`	`borg2 rdelete REPO`
List archives	`borg list REPO`	`borg2 list REPO`
Archive info	`borg info REPO::ARC`	`borg2 info REPO::ARC`
Create	`borg create REPO::ARC src/`	`borg2 create REPO::ARC src/`
Extract	`borg extract REPO::ARC`	`borg2 extract REPO::ARC`
Prune	`borg prune REPO`	`borg2 prune REPO`
Compact	N/A (auto)	`borg2 compact REPO` (REQUIRED after delete/prune)
Check	`borg check REPO`	`borg2 check REPO`
Mount	`borg mount REPO::ARC MNTPT`	`borg2 mount REPO::ARC MNTPT`

Create a temporary test repo inside the container

When you need a throwaway repo to test against:

bash

# Create a temp repo (unencrypted for easy testing)
docker exec -u borg borg-web-ui bash -c "
  BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=yes \
  borg init --encryption=none /tmp/test-repo-1 2>&1 &&
  echo 'test content' > /tmp/testfile.txt &&
  borg create /tmp/test-repo-1::archive-1 /tmp/testfile.txt 2>&1 &&
  borg list /tmp/test-repo-1 2>&1
"

# Same for borg2
docker exec -u borg borg-web-ui bash -c "
  BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK=yes \
  borg2 rcreate --encryption=none /tmp/test-repo-2 2>&1 &&
  echo 'test content' > /tmp/testfile.txt &&
  borg2 create /tmp/test-repo-2::archive-1 /tmp/testfile.txt 2>&1 &&
  borg2 list /tmp/test-repo-2 2>&1
"

JSON output for parsing

Always prefer --json flag to get structured output you can map directly to Python:

bash

docker exec -u borg borg-web-ui bash -c "borg list --json /tmp/test-repo-1 2>&1"
docker exec -u borg borg-web-ui bash -c "borg info --json /tmp/test-repo-1::archive-1 2>&1"
docker exec -u borg borg-web-ui bash -c "borg2 rinfo --json /tmp/test-repo-2 2>&1"

Inspect the Python app code live

bash

# Check what Python modules are available
docker exec borg-web-ui bash -c "cd /app && python3 -c 'from app.core.borg2 import *; print(\"ok\")'"

# Run a quick Python snippet against the live app
docker exec borg-web-ui bash -c "cd /app && python3 -c \"
import asyncio
from app.core.borg2 import borg2_rinfo
result = asyncio.run(borg2_rinfo('/tmp/test-repo-2'))
print(result)
\""

Cleanup

After debugging, clean up temp repos:

bash

docker exec borg-web-ui bash -c "rm -rf /tmp/test-repo-1 /tmp/test-repo-2 /tmp/testfile.txt"

Rules

Always run the command first, then write code — never guess borg output format.
Use --json wherever possible — map the exact field names into Python dicts.
Capture stderr — borg sends warnings and errors to stderr; use 2>&1.
Test both binaries — when working on borg2 features, also verify borg1 is unaffected.
Clean up temp repos after debugging sessions.
If container is not running, tell the user before attempting anything.

Files

Just SKILL.md in .claude/skills/borg-live-debug of karanhudia/borg-ui.

Open the folder on GitHubat commit 196a74a

Compare with similar skills

Borg Live Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Borg Live Debug compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Borg Live Debug this skillkaranhudia/borg-ui	1.7k	—	~1.4k	Automated safety check: Notes	AGPL-3.0	yesterday
.NET Crash Dump Collectiondotnet/skills	5.6k	2 repos	~1.1k	Automated safety check: Pass	MIT	today
Medusa Cloud Local Buildmedusajs/medusa-agent-skills	227	—	~1k	Automated safety check: Notes	None	3 days ago
Debug Firewallgithub/gh-aw-firewall	148	—	~1.2k	Automated safety check: Notes	MIT	today
Hermes S6 Container Supervisionjohnson7788/MultiUserClaw	327	—	~2.8k	Automated safety check: Notes	MIT	1 mo ago
CLI Testingvellum-ai/vellum-assistant	1.4k	—	~1.6k	Automated safety check: Pass	MIT	yesterday

Similar skills

.NET Crash Dump Collection
dotnet/skills
Official
Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.
5.6k GitHub starsUsed in 2 repos~1.1k tokens
DevOps & CloudAuto-check passed
Medusa Cloud Local Build
medusajs/medusa-agent-skills
Reproduces a Medusa Cloud build on your machine with mcloud local build, to debug build-failed deployments without pushing or waiting on Cloud.
227 GitHub stars~1k tokensUpdated 3 days ago
DevOps & CloudAuto-check: notes
Debug Firewall
github/gh-aw-firewall
Official
Debug the AWF firewall by inspecting Docker containers (awf-squid, awf-agent), analyzing Squid access logs, checking iptables rules, and troubleshooting blocked domains or network issues.
148 GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check: notes
Hermes S6 Container Supervision
johnson7788/MultiUserClaw
Modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image — adding new services, debugging profile gateways, understanding the Architecture B main-program pattern.
327 GitHub stars~2.8k tokensUpdated 1 mo ago
DevOps & CloudAuto-check: notes
CLI Testing
vellum-ai/vellum-assistant
Manually test a running Vellum assistant end-to-end purely from the CLI — no desktop app or web UI.
1.4k GitHub stars~1.6k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Deploying To Azure
microsoft-foundry/foundry-agent-webapp
Provides deployment commands and troubleshooting for Azure Container Apps.
127 GitHub stars~2.2k tokensUpdated 5 mo ago
DevOps & CloudAuto-check: warnings

Questions about Borg Live Debug

What does Borg Live Debug do?

Live Borg debugging by exec-ing into the borg-web-ui Docker container. Borg Live Debug is an agent skill from karanhudia/borg-ui. Live Borg debugging by exec-ing into the borg-web-ui Docker container.

When should I use Borg Live Debug?

Borg Live Debug fits situations like: debugging borg commands; writing tests against real borg output; developing borg 2.0 features; verifying borg behavior before writing code.

How do I install Borg Live Debug in Claude Code?

Run `npx skills add karanhudia/borg-ui --skill borg-live-debug -a claude-code`. Or copy the skill folder (.claude/skills/borg-live-debug in karanhudia/borg-ui) into .claude/skills/borg-live-debug in your project. Claude Code loads it when a task matches its description.

How do I install Borg Live Debug in Codex?

Run `npx skills add karanhudia/borg-ui --skill borg-live-debug -a codex`. Or copy the skill folder (.claude/skills/borg-live-debug in karanhudia/borg-ui) into .agents/skills/borg-live-debug in your project. Codex loads it when a task matches its description.

Can I use Borg Live Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add karanhudia/borg-ui --skill borg-live-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/borg-live-debug, .gemini/skills/borg-live-debug, .github/skills/borg-live-debug and .opencode/skills/borg-live-debug in your project.

What does Borg Live Debug need to run?

Going by SKILL.md and its folder, Borg Live Debug needs the command-line tools its instructions call (docker and python3). Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Bash, Read, Edit, Write, Grep, Glob.

Does Borg Live Debug access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Borg Live Debug safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Borg Live Debug use?

Borg Live Debug is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Borg Live Debug use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Borg Live Debug?

Skills that share tags, products or a category with Borg Live Debug: .NET Crash Dump Collection (dotnet/skills, 5.6k stars), Medusa Cloud Local Build (medusajs/medusa-agent-skills, 227 stars), Debug Firewall (github/gh-aw-firewall, 148 stars) and Hermes S6 Container Supervision (johnson7788/MultiUserClaw, 327 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Borg Live Debug?

karanhudia (a GitHub user) maintains it in karanhudia/borg-ui, which has 1,656 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

Source: karanhudia/borg-ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Borg Live Debug

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Borg Live Debug Skill

Container Details

How to exec into the container

Workflow

Step 1 — Verify the container is running

Step 2 — Probe the environment

Step 3 — Run the borg command and capture output

Step 4 — Use output to write code

Common borg2 command cheat sheet (key differences from borg1)

Create a temporary test repo inside the container

JSON output for parsing

Inspect the Python app code live

Cleanup

Rules

Files

Compare with similar skills

Similar skills

More from karanhudia/borg-ui

Related

Questions about Borg Live Debug