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/lock)<a href="https://agentmods.dev/commands/joaquinbejar/ai-crew-sync/lock"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/lock/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/lock"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/lock.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.00014 | $0.00237 |
| Opus 5.5 | $0.00006 | $0.00095 |
| Sonnet 5.5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
lock 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
Take a lock on a shared resource through the crew bus.
Input: $ARGUMENTS
Steps:
- The first word is the resource name, e.g.
deploy:stagingorschema:users. A second numeric word is the TTL in minutes (default 30). The rest is the purpose; if empty, use one line from what I am doing. - Call
acquire_lockwithname,ttl_seconds= minutes × 60, andpurpose. - If it is refused, report verbatim who holds it, why, and when it expires. Do not retry in a loop; offer to wait for it with
wait_for_updates(kinds: ["lock"], thewaitrecipe) to be told when it frees up.
Confirm with the name, the expiry, and the reminder: release_lock (the unlock recipe) when I am done; the lock expires on its own otherwise.
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 · 16 lines · 14 tokens per session scan A 22273eaa92d9
lock is a command published in the GitHub repository joaquinbejar/ai-crew-sync (8 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 237 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.
project-groups
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
sddp-devops
Command description: Create or refine the deployment and operations document. Argument hint: [project description, infrastructure context, deployment constraints, or operations inputs] Command category: project-bootstrap Prerequisites: none.
migrating-fabric-trial-capacities
Migrate workspaces from trial capacity to production capacity.
jira-issue-use-aws
Same as /jira-issue, plus an AWS deep-dive — diagnose the reported symptom through the operator's live AWS CLI session using strictly read-only calls (logs, metrics, resource state, CloudTrail) before filing the groomed Jira issue with cloud-traced evidence. Example — /jira-issue-use-aws "file export" presigned…
twining:status
Show Twining project coordination status.