Borrowing it
Nothing to install: this file belongs to tatargabor/set-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tatargabor/set-core/main/.claude/commands/set/broadcast.mdgit clone --depth 1 https://github.com/tatargabor/set-coreWrote 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/commands/tatargabor/set-core/broadcast)<a href="https://agentmods.dev/commands/tatargabor/set-core/broadcast"><img src="https://agentmods.dev/badge/commands/tatargabor/set-core/broadcast.svg" alt="Measured on agentmods" 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.00000 | $0.00256 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
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 today.
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.
What it actually says
Broadcast what you're working on to other agents.
Usage: /set:broadcast <message>
Input: The argument after the command is the broadcast message — a short free-form description of what you're currently working on.
What to do:
- Read the current
.wt/activity.jsonif it exists (to preserveskill,skill_args,modified_files) - Update or create
.wt/activity.jsonwith the broadcast message and current timestamp - The file format:
{
"skill": "<preserved from existing>",
"skill_args": "<preserved from existing>",
"broadcast": "<the message from the user>",
"modified_files": "<preserved from existing>",
"updated_at": "<current ISO8601 UTC timestamp>"
}
- Confirm the broadcast was set
Important:
- The broadcast field OVERWRITES the previous broadcast (not append)
- Preserve all other existing fields from activity.json
- If activity.json doesn't exist, create it with just broadcast and updated_at
- Use UTC timestamps in ISO8601 format (e.g., "2026-02-07T21:00:00Z")
ARGUMENTS: $ARGUMENTS
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.
- today First seen · 30 lines · 0 tokens per session scan A 682817367961
broadcast is a command published in the GitHub repository tatargabor/set-core (35 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 256 tokens. 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-09-06.
Other commands, from other repositories
hatch3r-workflow
Guided development lifecycle with 4 phases (Analyze, Plan, Implement, Review) and scale-adaptive Quick Mode for small tasks; --plan-file executes an approved plan document without re-deriving it.
hatch3r-incident-response
Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents.
optimize
Show TokenJam's savings/optimize report — where quota is going and what's recoverable. Equivalent to running tj optimize.
doctor
Run TokenJam's health check — config, ingest endpoint, and storage. Equivalent to running tj doctor.
manager
CRUD command router for managing SYNAPSE domains, rules, and star-commands.
greet
Generate contextual agent greeting using GreetingBuilder infrastructure.