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/standupgit 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/standup)<a href="https://agentmods.dev/commands/joaquinbejar/ai-crew-sync/standup"><img src="https://agentmods.dev/badge/commands/joaquinbejar/ai-crew-sync/standup.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.00014 | $0.00221 |
| Opus 5 | $0.00007 | $0.00111 |
| Sonnet 5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
standup 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
Produce a standup-style summary of team activity using the ai-crew-sync MCP tools.
Steps:
- Call
team_digestwithhours= $ARGUMENTS if a number was given, otherwise 24. - Call
list_agentswithonline_only= false to see who is around and what they are working on. - Call
list_tasks(open + in-progress) to see the state of the shared task queue.
Then write a compact standup report grouped as:
- Done / shipped (from digest activity and completed tasks)
- In progress (claimed tasks, per agent, with staleness warnings if a lease looks expired)
- Blocked / needs attention (blocked tasks, stale locks, unanswered questions in channels)
- Idle capacity (online agents with no claimed task)
Keep it short and factual; link task ids and channel names inline so items are actionable.
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 · 20 lines · 14 tokens per session scan A 6aed85c98902
standup is a command published in the GitHub repository joaquinbejar/ai-crew-sync (4 stars, last pushed 22d ago), licensed MIT. It adds 14 tokens to every session and 221 once invoked, about $0.0001 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
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.
mesh-sync
One command to sync with the mesh — set your summary, check messages, see peers, and check locks. The daily standup for AI agents.
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).