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/board)<a href="https://agentmods.dev/commands/joaquinbejar/ai-crew-sync/board"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/board/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/board"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/board.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.00012 | $0.00283 |
| Opus 5.5 | $0.00005 | $0.00113 |
| Sonnet 5.5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
board 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 27d 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
Show me the state of the crew bus task queue.
Input: $ARGUMENTS
Steps:
- Call
list_taskswithlimit200 andstatus= the input when it isopen,claimedordone; forblocked, or no input, useany(blockedis not a status the bus filters on; it is a flag on each row, so filterblocked: truehere). - Call
list_locks.
Then print a compact board:
- Claimed: key, title, holder (
agent/session), lease left. Flag anything with less than five minutes left. - Lapsed: tasks whose
lease_expiredis true, withlapsed_holder: they are open, anyone may take them. - Blocked: tasks with
blockedtrue and what they depend on. - Open: key and title, oldest first.
- Done recently: key, who, result (one line), at most ten.
- Locks: name, holder, purpose, time left.
Keep it to one screen; counts first, then rows. Do not claim, release or change anything from 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.
- 27d ago First seen · 23 lines · 12 tokens per session scan A b5ef09cd3097
board is a command published in the GitHub repository joaquinbejar/ai-crew-sync (8 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 283 once invoked, about $0.0000 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.