Ingeniería
A 5-minute routine costs ~12× an hourly one
Same bot, same prompt — the clock is what burns the allowance.
Qué dolía
Ruslan (@RDV1113) full course: one routine every 5 minutes wakes ~8,640 times/month (~$400 at API rates vs ~$33 hourly). On a subscription you see allowance burn, not a line item. His rules: event triggers over polling, slowest schedule the job can live with, cheap "did anything change?" gate before expensive work, never let a night routine wait for approval, keep your own run log (product keeps ~20). Not affiliated with xAI.
Qué instalar o crear
Audit routine intervals. Slow what can wait; gate fast checks; log runs yourself.
Bots
Ningún bot nuevo. Sigue los pasos del primer uso.
Plugins
Ninguno el primer día. Sigue los pasos del primer uso.
Archivos
routine-run-log.md. Your log of routine fires and whether anything changed.
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
El prompt
Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.
Primer uso
- 1Read https://x.com/RDV1113/status/2109581928907034894 (credit @RDV1113).
- 2List every routine and its interval.
- 3For each: switch to event trigger if possible, else the slowest schedule that still works.
- 4Add a cheap change-detect step before expensive work on any remaining fast routine.
- 5Start a personal run log; never leave overnight routines blocked on your approval.
Valla de aprobación
Do not enable new sub-hourly routines without your yes.
Qué ajustar
Steal the cadence math. Frequency is a cost knob, not a virtue.
Fuente
Ruslan Dranovskiy @RDV1113 · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
Routine cost control: stop running out of usage by Wednesday
A one-hour audit, a quiet Usage officer and a fix playbook (cadence, silence, event triggers, fresh chats, scripts over clicks) that cut waste without losing the jobs your bots do.