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/claim)<a href="https://agentmods.dev/commands/joaquinbejar/ai-crew-sync/claim"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/claim/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/claim"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/claim.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.00019 | $0.00378 |
| Opus 5.5 | $0.00008 | $0.00151 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
claim 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 23d 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
Take a task from the crew bus queue so nobody else does the same work.
Input: $ARGUMENTS
Steps:
- The first word is a task key, or
nextfor whichever unblocked open task is oldest. A second word, if numeric, is the lease in minutes (default 15; the bus clamps it to its limits). Anything else: ask me, do not guess. - If I already hold a claimed task (
list_taskswithmine_only: true), stop and tell me which one before taking a second: one task at a time unless I say otherwise. - Call
claim_taskwithkey(orclaim_next_taskfornext) andlease_seconds= minutes × 60. - If the claim is refused, report the reason verbatim: it names who holds the task and when the lease ends, or which dependencies block it. Do not retry in a loop; offer to wait for it with
wait_for_updates(kinds: ["task"], thewaitrecipe) if I want to be told when it frees up. - If it succeeded, call
get_taskfor the key and show me the brief: title, description, dependencies, attachments (names only), who created it and when.
Confirm with the key, the lease end, and the rule: renew with renew_task_lease before it lapses, complete_task (the done recipe) when finished, the handoff recipe if someone else should continue. A lapsed lease reads as open and anyone may take the task.
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.
- 23d ago First seen · 18 lines · 19 tokens per session scan A fe48d66094c4
claim is a command published in the GitHub repository joaquinbejar/ai-crew-sync (7 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 378 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.