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-subscribegit 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-subscribe)<a href="https://agentmods.dev/skills/band-app/band/band-subscribe"><img src="https://agentmods.dev/badge/skills/band-app/band/band-subscribe/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-subscribe"><img src="https://agentmods.dev/badge/skills/band-app/band/band-subscribe.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.00139 | $0.01377 |
| Opus 5.5 | $0.00056 | $0.00551 |
| Sonnet 5.5 | $0.00028 | $0.00275 |
| Haiku 4.5 | $0.00014 | $0.00138 |
Grade A, and why
band-subscribe 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Band Subscribe
A subscription tells Band what the current chat is waiting for. The agent subscribes, ends its turn, and Band sends a short follow-up message into the same chat when a matching event arrives. Nothing polls and no loop keeps a session open.
Related skills:
band-loopruns a fixed prompt on a schedule. Use it for recurring work. Use a subscription when the work starts when something happens.band-chatmanages chat panes.
Prerequisites
- The Band server is running.
- The agent runs inside a Band chat. Band sets
BAND_CHAT_IDandBAND_WORKTREE_IDthere, andband subscriptionsuses them as defaults. A terminal has no chat, so outside a chat pass--chat <id>.
When to subscribe
- After opening a PR. Subscribe to its reviews and CI:
band subscriptions create --pr owner/repo#N --reviews --ci. - After asking a question and waiting for the answer in a channel or a PR comment. Subscribe to the thread, PR or webhook that carries the answer.
- When the user asks to wait. A one-off timer (
--at 30m) covers "check back in half an hour". A cron timer (--cron "0 9 * * *") covers a morning check.
Subscribe once per thing waited for, then end the turn. Do not poll gh in a loop.
When to unsubscribe
Remove a subscription as soon as the wait is over: the PR merged or closed, CI passed and nobody is reviewing, the question was answered. A subscription also ends by itself after --max-wakeups wakeups (default 10 for CI, 50 otherwise, one for a one-off timer) and after 180 days.
band subscriptions list
band subscriptions remove sub_abc123
Commands
band subscriptions create
Exactly one of --pr, --branch, --webhook, --cron, --at.
| Flag | Meaning |
|---|---|
--pr owner/repo#N |
Reviews, review comments, comments and lifecycle events (merged, closed) of one PR. |
--reviews, --comments |
With --pr. Reviews and comments are one subscription, so either flag creates it. With neither flag and no --ci, it is created too. |
--ci |
With --pr, also watches CI on the PR's head branch (looked up with gh). One result per commit, sent after every check finishes. |
--branch owner/repo@branch |
CI result of a branch, once per commit. Same as --ci without a PR. |
--webhook |
A webhook that wakes the chat. Prints POST /api/hooks/<id> and a token, shown once. Send the token in X-Band-Webhook-Token. |
--cron "<expr>" |
Recurring timer. Standard cron, seconds field optional. |
--at <when> |
One-off timer. Epoch milliseconds, or a delay: 90s, 10m, 2h, 1d. |
--max-wakeups N |
Stop after N wakeups. |
--coalesce S |
Seconds to hold events so a burst wakes the chat once (default 30). |
--chat, --worktree |
Override BAND_CHAT_ID and BAND_WORKTREE_ID. |
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 b55626e9577a
- 26d ago First seen · 102 lines · 139 tokens per session scan A 49f11e26dfea
band-subscribe is a skill published in the GitHub repository band-app/band (5 stars, last pushed today), licensed MIT. It adds 139 tokens to every session and 1,377 once invoked, about $0.0006 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-10-04.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.