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 stevengonsalvez/agents-in-a-box --skill broadcastgit clone --depth 1 https://github.com/stevengonsalvez/agents-in-a-boxWrote 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/stevengonsalvez/agents-in-a-box/broadcast)<a href="https://agentmods.dev/skills/stevengonsalvez/agents-in-a-box/broadcast"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/broadcast/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/stevengonsalvez/agents-in-a-box/broadcast"><img src="https://agentmods.dev/badge/skills/stevengonsalvez/agents-in-a-box/broadcast.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.00114 | $0.00915 |
| Opus 5 | $0.00057 | $0.00458 |
| Sonnet 5 | $0.00023 | $0.00183 |
| Haiku 4.5 | $0.00011 | $0.00092 |
Grade A, and why
ainb-fleet:broadcast 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 11d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ainb fleet:broadcast
Send one prompt to selected sessions. Mandatory targeting flag.
Run
ainb fleet broadcast "<prompt>" --all # every running session
ainb fleet broadcast "<prompt>" --filter "<regex>" # match tmux/workspace name
ainb fleet broadcast "<prompt>" --cwd "<substring>" # match cwd
Targeting flags (one required)
| flag | matches against |
|---|---|
--all |
every session in ainb fleet standup |
--filter <regex> |
regex against tmux_session OR workspace_name |
--cwd <substring> |
substring against cwd |
If none provided, the command exits with broadcast requires --all, --filter <regex>, or --cwd <substring> — by design, to prevent
accidental fan-out.
Output
ainb fleet broadcast — sent to N target(s)
✓ <name> via tmux <tmux_session>
✓ <name> via broker peer <peer_id>
✗ <name>: <reason>
✓ via tmux = sent via tmux send-keys -l (literal mode, works for any
tmux pane regardless of peer state) — this is the default path.
✓ via broker = sent through claude-peers HTTP — only seen when a target
has no live tmux pane (or AINB_FLEET_TRANSPORT=peers is set).
Routing rule
Controlled by AINB_FLEET_TRANSPORT (default tmux-first). For each target:
Default (tmux-first):
- If session has
tmux_sessionand tmux says it exists →tmux send-keys -l. - Else if session has
peer_idand broker is healthy → POST/send-messageto broker. - Else →
Failed { reason: "no live tmux session and no reachable broker peer" }.
tmux-only: step 1 only; never touches the broker. Failure reason notes
(transport=tmux-only).
peers / broker (legacy): the old order — broker first, tmux fallback.
Common flows
Cycle a specific app:
ainb fleet broadcast "/clear" --filter "shotclubhouse"
Pull latest in every active worktree:
ainb fleet broadcast "git pull" --cwd "/agents-in-a-box/worktrees/"
Universal reset:
ainb fleet broadcast "/exit" --all # careful — quits everything
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.
- 11d ago First seen · 111 lines · 114 tokens per session scan A 5f44abf094a9
ainb-fleet:broadcast is a skill published in the GitHub repository stevengonsalvez/agents-in-a-box (23 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 915 once invoked, about $0.0006 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-30.
Other skills, from other repositories
chinese-git-workflow
A Git workflow guide tailored to Chinese-hosted platforms such as Gitee, Coding.net, and GitLab, including their code-review and build systems.
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.
using-superpowers
A set of rules for finding and using assistant skills at the start of every conversation. It says to check for relevant skills before responding, including when asking a clarification question.
chinese-code-review
Chinese-language guidance for giving professional, tactful code-review feedback while still calling out real problems.
mcp-builder
A guide to building MCP servers, which let AI assistants call tools or read connected data. It covers server structure, tool design, validation, testing and deployment in TypeScript and Python.
platform-api
Queries the Genesys Cloud Platform API schema for endpoint details, permissions, parameters, and response formats. Use when user asks about Genesys Cloud API endpoints (e.g., "/api/v2/assistants/queues"), API documentation, API permissions, schemas, capabilities, or when implementing Genesys Cloud operations.