What is async-standup?

An asynchronous stand-up tool that collects each developer's daily update and compiles the responses. A stand-up is a short team report about recent work, planned work, and blockers; asynchronous means people respond at different times.

Use it to start a reporting period, send reminders through a configured channel, track responses, and compile the reports.

It avoids requiring the whole team to meet at the same time while still producing a shared daily status report.

async-standup — Command for Claude Code by gonzalezpazmonica

Install

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.

Clone the repo

git clone --depth 1 https://github.com/gonzalezpazmonica/savia

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/async-standup/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/savia/async-standup)

Your own site

<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/async-standup"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/async-standup/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/async-standup"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/async-standup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,007 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.01007
Opus 5	$0.00014	$0.00504
Sonnet 5	$0.00005	$0.00201
Haiku 4.5	$0.00003	$0.00101

Measured 3d ago against content hash ad4c0d69e1f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

async-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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

async-standup — 100% identical, 0 lines differ

.claude/commands/async-standup.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/async-standup

🦉 Standup asíncrono: cada dev reporta a su ritmo, Savia compila el reporte diario.

Parámetros

--project {nombre} — Proyecto de PM-Workspace (obligatorio)
--channel — Canal WhatsApp/Slack/Talk para recolectar reports (si no especificado: usar STANDUP_CHANNEL)
--compile — Compilar reports recolectados hasta ahora (defecto)
--start — Iniciar período de recolección (envía mensaje recordatorio a equipo)
--deadline {HH:MM} — Hora límite compilación (defecto: 15:00)
--list — Listar reports pendientes y completados

Contexto requerido

projects/{proyecto}/CLAUDE.md — Config del proyecto
projects/{proyecto}/team.md — Miembros del equipo y contactos
docs/rules/domain/messaging-config.md — Canales de mensajería

Pasos de ejecución

Fase 1 — Iniciar recolección (--start)

Leer equipo de team.md

Enviar mensaje recordatorio a cada miembro por WhatsApp/Slack/Talk:

🦉 Standup asíncrono de {proyecto} abierto hasta {deadline}.
Reporta: ¿Ayer qué hiciste? ¿Hoy qué harás? ¿Bloqueantes?
Responde con: /standup-report [tuNombre]

Iniciar período de escucha (modo inbox)
Mostrar confirmación

Fase 2 — Recolectar reports

Escuchar mensajes en canal designado. Detectar patrones:

Primer mensaje: identificar dev por nombre
Estructura esperada: "ayer: X | hoy: Y | bloqueantes: Z"
Aceptar variaciones de redacción (NLP flexible)

Guardar cada report en {proyecto}/standups/YYYYMMDD/{dev}.txt

Fase 3 — Compilar reporte (--compile)

Leer todos los reports recolectados hasta las {deadline}
Agrupar por estado: "ayer", "hoy", "bloqueantes"
Detectar patrones:
- Bloqueantes recurrentes → sugerir escalación
- Dependencias cruzadas → señalar
- Desvíos de velocidad → alertar
Generar markdown:

## Async Standup — {proyecto} — {YYYY-MM-DD}

### Participación: 7/8 (87.5%)
Falta reportar: Carlos

### Ayer (Sprint 2026-NN)
- Ana: Finalizar integración pagos + code review de Pedro
- Pedro: Tests unitarios backend, 4/5 completados
- María: Documentación API, 80% avance
...

### Hoy (prioridad del sprint)
- Ana: Deploy PRE de pagos, validación PO
- Pedro: Terminar tests, PR review, standup técnico
- María: Completar docs, generar diagrama OpenAPI
...

### 🚨 Bloqueantes
1. **Pedro**: "Dependencia de Ana para config de API keys PRE"
2. **Carlos**: "No llegó a reportar — seguimiento pendiente"

### Patrones detectados
- Dolor: Testing (mencionado 3 veces) → 3 sprints consecutivas
- Alerta: Config PRE sin documentar (riesgo deploy)
- Oportunidad: Pair María + Ana para acelerar docs

### Próximos pasos sugeridos
1. Resolver bloqueante PRE keys: meeting rápido Ana + Pedro
2. Seguimiento a Carlos (Viernes)
3. Considerar docu técnica como task separada sprint próximo

Read the full file on GitHub · 118 lines

Changes

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.

3d ago First seen · 118 lines · 27 tokens per session scan A ad4c0d69e1f6

Subscribe to this mod's changes

async-standup is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,007 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-09-06.

Claude Code Project management codex harness opencode

async-standup

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

/async-standup

Parámetros

Contexto requerido

Pasos de ejecución

Fase 1 — Iniciar recolección (--start)

Fase 2 — Recolectar reports

Fase 3 — Compilar reporte (--compile)

What this file has done since we first saw it

Other commands, from other repositories

wtfp:contribute

project-skill

project-brief

tickets-implement

hive

status