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 skills/kevinzai/commander/ccc-broadcastnpx skills add KevinZai/commander --skill ccc-broadcastgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-broadcast)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-broadcast"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-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 | $0.00041 | $0.01567 |
| Opus 5 | $0.00020 | $0.00783 |
| Sonnet 5 | $0.00008 | $0.00313 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
ccc-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 5d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-broadcast — Outbound Status Relay
Placeholders like
~~chatand
Turn "did the deploy work?", "is the site up?", and "did the overnight run finish?" into pushed status updates. ccc-broadcast watches the operational signals a CC Commander session already produces — builds, deploys, CI results, task completions, cost/budget alerts — and relays a plain-language summary to the channels a team actually reads (~~chat, ~~email). No dashboards to open, no terminal to babysit.
This is the outbound-status counterpart to $ccc-nightwatch (which relays approval requests to your phone). Nightwatch asks "can I do this?"; broadcast tells "here's what happened."
What it does
The skill maps CC Commander lifecycle events to a small set of business-legible messages and forwards them through whatever ~~chat or ~~email connector is enabled via $ccc-connect. Each relay is a short, scrubbed summary — event type, human outcome, and a link if one exists — never file contents, diffs, or secret values. Signals are classified by audience so engineers, owners, and clients each get the right altitude.
Triggers
$ccc-broadcast- "tell the team when the deploy finishes"
- "send me a status when the build is done"
- "broadcast ops updates to Slack"
- "let the client know when it's live"
- "team status updates"
Signal → Audience Matrix
| Signal | Example | Default audience | Channel |
|---|---|---|---|
| 🟢 Ship | Deploy succeeded, site live | Owner + team | ~~chat |
| 🧪 CI | Tests green / red on a branch | Team | ~~chat |
| ✅ Task done | Overnight run / feature complete | Owner | ~~chat or ~~email |
| 💰 Cost | Budget threshold crossed (80% / 100%) | Owner | ~~email |
| 🔴 Incident | Deploy failed, error spike | Team (immediate) | ~~chat |
| 🗒️ Digest | End-of-day rollup of the above | Owner | ~~email |
Unclassified signals default to the 🗒️ digest (batched, low-noise).
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.
- 5d ago First seen · 142 lines · 41 tokens per session scan A 58f9cfe59cf1
ccc-broadcast is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,567 once invoked, about $0.0002 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.
Other skills, from other repositories
operating-infra
Author, inspect, troubleshoot, and review infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions workflow/job/permissions semantics, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances…
gitlab-cli
GitLab CLI (glab) wrapper for MR status, issues, and repository operations.
ci-cd-pipeline-builder
Tier: POWERFUL Category: Engineering Domain: DevOps / Automation.
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.