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 skills add band-app/band --skill band-startgit clone --depth 1 https://github.com/band-app/bandWrote 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/skills/band-app/band/band-start)<a href="https://agentmods.dev/skills/band-app/band/band-start"><img src="https://agentmods.dev/badge/skills/band-app/band/band-start/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/skills/band-app/band/band-start"><img src="https://agentmods.dev/badge/skills/band-app/band/band-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.03808 |
| Opus 5.5 | $0.00030 | $0.01523 |
| Sonnet 5.5 | $0.00015 | $0.00762 |
| Haiku 4.5 | $0.00008 | $0.00381 |
Grade A, and why
band-start 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start a Band Worktree
Creates a Band worktree (git worktree) and submits a task to the coding agent in a single step. The only required input is the prompt — a natural-language description of what the agent should work on. This skill figures out the repo, branch name, and any ticket context automatically.
This skill is focused on the kickoff flow. For broader operations see the sibling skills:
band— worktrees, repos, cronjobs, tunnel, settings.band-chat— chat panes inside a worktree (band chats send/watch/...).band-loop— schedule a recurring prompt against a worktree (band cronjobs ...).band-terminal— terminal sessions inside a worktree.band-browser— browser tabs inside a worktree.
Prerequisites
- The Band server must be running (started by the Band dashboard app). Connects to
http://localhost:3456by default. - The target repo must be registered with Band (
band repos listto check). - Optional:
aclifor Jira ticket lookups,ghfor GitHub issue lookups. Missing tools are non-fatal — the skill falls back to using the prompt as-is.
JSON Output
All commands support --output json (or BAND_OUTPUT=json env var) for structured output.
- Success: JSON object to stdout, exit code 0
- Error:
{"error": "message"}to stderr, exit code 1
Workflow
1. Determine the repo
Match the current working directory against the registered Band repos:
band repos list --output json | jq -r '.repos[] | "\(.name)\t\(.path)"'
Pick the repo whose path is the cwd or one of its ancestors. If no match or the cwd is ambiguous (multiple registered repos under the same root), ask the user to pick one.
1a. Plain (non-git) repos: short-circuit
A Band repo can be either a git repo (the normal case) or a "plain" folder (no .git). Plain repos have a single implicit worktree whose path equals the repo path — there are no branches, no PRs, no worktrees create.
After step 1, check the repo's kind field:
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.
- 25d ago Changed · +2 tokens per session 1ec1f4aece9b
- 2mo ago First seen · 302 lines · 74 tokens per session scan A cdbea83ffda0
band-start is a skill published in the GitHub repository band-app/band (5 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 3,808 once invoked, about $0.0003 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-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…