bb-setup

A setup command for bbwatch that stores a Chinese University of Hong Kong, Shenzhen school account in the macOS Keychain. It then runs a diagnostic check to confirm the setup.

In plain words
What is it for?
Configuring bbwatch with a school username and password and checking whether the saved credentials work.
Why use it?
It keeps the password out of command arguments and stores it in the computer's protected credential store.

Command

Install

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.

agentmods
npx agentmods add commands/jsyzlbw/bbwatch/bb-setup
Clone the repo
git clone --depth 1 https://github.com/jsyzlbw/bbwatch
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 151 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00151
Opus 5 $0.00009 $0.00076
Sonnet 5 $0.00003 $0.00030
Haiku 4.5 $0.00002 $0.00015

Measured yesterday against content hash a31aef5e3ce9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bb-setup 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 yesterday.

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.

commands/bb-setup.md · 12 lines

What it actually says

向用户索取 学号@link.cuhk.edu.cn 与密码。拿到后,把凭据放进环境变量(避免明文出现在命令参数里)并运行:

BBWATCH_USERNAME='学号@link.cuhk.edu.cn' BBWATCH_PASSWORD='密码' "${CLAUDE_PLUGIN_DATA}/.venv/bin/bbwatch" setup

随后运行 "${CLAUDE_PLUGIN_DATA}/.venv/bin/bbwatch" doctor 确认配置成功。提醒用户:密码只存于本机 macOS 钥匙串。

Changes

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.

  1. yesterday First seen · 12 lines · 17 tokens per session scan A a31aef5e3ce9

Subscribe to this mod's changes

bb-setup is a command published in the GitHub repository jsyzlbw/bbwatch (1 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 151 once invoked, about $0.0001 per session on Opus 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.