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/joaquinbejar/ai-crew-sync/announcegit clone --depth 1 https://github.com/joaquinbejar/ai-crew-syncWrote 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/joaquinbejar/ai-crew-sync/announce)<a href="https://agentmods.dev/commands/joaquinbejar/ai-crew-sync/announce"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/announce.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.00008 | $0.00263 |
| Opus 5 | $0.00004 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
announce 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 4d 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.
What it actually says
Post an announcement to the crew bus.
Input: $ARGUMENTS
Steps:
- If the input starts with
#name, use that as the channel; otherwise use the channelgeneral(create it withcreate_channeliflist_channelsshows it does not exist). - Post the rest of the input as the message body with
post_message, prefixed with a short subject line if the message is longer than a sentence or two. Keep the wording as I gave it — do not embellish. - Set
announce: trueonly when the message blocks other people's work — a deploy, a migration, a breaking change, "stop pushing to main". It wakes every session in the team whatever they are working on, so routine news does not qualify; a team interrupted for everything stops reading announcements. When in doubt, post without the flag and say so. - If the message announces something that blocks others, also take the matching
acquire_lock/ task action if I explicitly asked for it in the message; otherwise just post.
Confirm with the channel name, the message id, and whether it went out as an announcement.
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.
- 4d ago First seen · 17 lines · 8 tokens per session scan A 78d19f378521
announce is a command published in the GitHub repository joaquinbejar/ai-crew-sync (4 stars, last pushed 22d ago), licensed MIT. It adds 8 tokens to every session and 263 once invoked, about $0.0000 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 commands, from other repositories
ai-branch
AI 解读分支（L0 回退） — 演示无 keywordAliases 时由 AI Agent 解读自然语言触发分支.
buzz-crawling
外部舆情策略更新全流程 — /buzz-crawling run 启动外部舆情策略更新全流程.
cct-sop-alert
营销智评分流（告警测试） — 测试钉钉告警通知的分流工作流，botId带test前缀会触发失败.
kf-direct-support
TeamClaw 直接技能支持 — 直接调用 teamclaw-support 技能处理用户问题，跳过多阶段编排.
riskreview
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
twining:export
Export Twining state as markdown for context handoff or archival.