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/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/async-standup)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/async-standup"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/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.
<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/async-standup"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/async-standup.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.00027 | $0.01007 |
| Opus 5 | $0.00014 | $0.00504 |
| Sonnet 5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
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 6d 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.
This is a copy
100% identical to async-standup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 proyectoprojects/{proyecto}/team.md— Miembros del equipo y contactosdocs/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
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.
- 6d ago First seen · 118 lines · 27 tokens per session scan A ad4c0d69e1f6
async-standup is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 4d ago), 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. It is 100% identical to async-standup, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.