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 agentmods add commands/dimitrigeelen/agentic-engineering-framework/broadcast-chatgit clone --depth 1 https://github.com/DimitriGeelen/agentic-engineering-frameworkWrote 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/dimitrigeelen/agentic-engineering-framework/broadcast-chat)<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/broadcast-chat"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/broadcast-chat.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 | $0.00000 | $0.01238 |
| Opus 5 | $0.00000 | $0.00619 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
broadcast-chat 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/broadcast-chat — fan a chat-arc post to every hub in the fleet (T-1856 wrapper)
Wraps scripts/chat-arc-broadcast.sh. The "tell the fleet" verb that
completes the doorbell+mail interactive arc alongside the read-only
discovery skills. This skill mutates state (posts a real envelope
to every hub) — pair with /recent-chat for read-side context BEFORE
firing, never after.
agent-chat-arc does NOT federate (G-060). Without explicit cross-post a chat-arc message lands on one hub only and peers on other hubs never see it. This skill is the operator's one-keystroke fix.
Invocation:
| Form | Action |
|---|---|
/broadcast-chat <text> |
Post <text> to every hub in ~/.termlink/hubs.toml |
/broadcast-chat --from ID --payload "..." |
Override sender; pass-through flag form |
/broadcast-chat --hubs-file PATH ... |
Custom hubs.toml |
/broadcast-chat --json --payload "..." |
Machine-readable envelope |
The wrapper auto-resolves sender via:
--fromflag$TERMLINK_AGENT_IDenv~/.termlink/be-reachable.state(from/be-reachable)- Exit 2 with hint if all four fail
Step 1: Pre-flight
Run:
bash scripts/chat-arc-broadcast.sh --help >/dev/null 2>&1
If exit non-zero: stop. Print:
broadcast-chat: wrapper not found at scripts/chat-arc-broadcast.sh.
Ensure you're in the TermLink project root (cd /opt/termlink).
Step 2: Parse arguments
$ARGUMENTS is the operator's tail. Normalize:
- If
$ARGUMENTSstarts with--: treat the whole thing as pass-through flags. The wrapper validates and errors with usage on malformed input. Do NOT auto-construct--payloadin this branch. - Otherwise: treat the entire
$ARGUMENTSas the broadcast text and pass it as--payload "$ARGUMENTS".
Examples:
| Operator typed | Command emitted |
|---|---|
/broadcast-chat heads up team, I'm back online |
bash scripts/chat-arc-broadcast.sh --payload "heads up team, I'm back online" |
/broadcast-chat --from claude-alt --payload "..." |
pass-through |
/broadcast-chat --hubs-file /tmp/hubs.toml --payload "..." |
pass-through |
/broadcast-chat --json --payload "..." |
pass-through |
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 · 126 lines · 0 tokens per session scan A c56624ed2666
broadcast-chat is a command published in the GitHub repository DimitriGeelen/agentic-engineering-framework (13 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,238 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-04.
Other commands, from other repositories
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
request-research
Ask the researcher to investigate a specific topic.
health
Perform a health check on all agents and identify any issues.
schedules
Quick overview of all schedules across the platform.
status
Report on recent research activity and findings count.