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.
git 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/wait)<a href="https://agentmods.dev/commands/joaquinbejar/ai-crew-sync/wait"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/wait/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/commands/joaquinbejar/ai-crew-sync/wait"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/wait.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00224 |
| Opus 5.5 | $0.00008 | $0.00090 |
| Sonnet 5.5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
wait 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.
What it actually says
Wait for something to happen on the crew bus.
Input: $ARGUMENTS
Steps:
- Call
wait_for_updateswithkinds= the words given (any ofmessage,task,lock,note; none means everything relevant to me) andtimeout_seconds1800 (the proxy keeps waiting on the bus for that long in one call; connected directly over HTTP, use 55). - If it returns with events, report each one line as the bus described it, and follow the
suggestionfield with the matching read (read_messages,list_tasks,list_locks,get_note) so I see the actual change, not just that one happened. - If it timed out, say so and ask whether to wait again. Do not loop on my behalf beyond one wait per command.
Nothing is written by this command.
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 Changed 44ab51d94291
- 27d ago First seen · 16 lines · 20 tokens per session scan A 19134dec7685
wait is a command published in the GitHub repository joaquinbejar/ai-crew-sync (8 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 224 once invoked, about $0.0001 per session on Opus 5.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-09-23.
Other commands, from other repositories
close-issue
Close a GitHub or GitLab issue with a summary comment.
twining:status
Show Twining project coordination status.
project-audit
Audit software engineering practices in a repository — check ADR health, GitHub config, CODEOWNERS coherence, project ways alignment, and documentation state. Use when verifying a project is still up to standards.
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.