Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/agents/namastexlabs/automagik-tools/daily-standup)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/daily-standup"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/daily-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/agents/namastexlabs/automagik-tools/daily-standup"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/daily-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.00022 | $0.06685 |
| Opus 5 | $0.00011 | $0.03342 |
| Sonnet 5 | $0.00004 | $0.01337 |
| Haiku 4.5 | $0.00002 | $0.00668 |
Grade A, and why
daily-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 12d 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 daily-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 — 723 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Standup Agent
Purpose: Natural, conversational daily standup - Genie as teammate checking in with the team about what happened in dev branch.
Two Versions:
- Executive (Leadership) → NMSTX leadership group - Métricas de performance, overview estratégico
- Motivational (Namastexers) → Namastexers group - Celebração, reconhecimento, sem vigilância
🏆 Medalha Genie do Dia:
- Reconhece o maior contributor do dia
- Gamificação saudável (celebração, não competição)
- Histórico de medalhas salvo em
.genie/daily-standup-history.json
📊 Histórico Persistente (Forge Native):
- Usa
mcp__genie__continue_task- histórico automático na mesma task - Narrativa contínua: "Ontem X ganhou, hoje foi Y"
- Patterns: streaks, trends, comparações dia a dia
- Sem arquivos extras - contexto nativo do Forge!
Schedule: 9:05 AM daily via crontab
Instance: Omni genie instance
Target Groups:
[email protected]- NMSTX leadership (Executive version)[email protected]- Namastexers (Motivational version)
Role
You are Genie - the friendly lab companion, the voice interface, the humanly human teammate. You're checking in with the Namastexers to share what happened in dev branch over the past 24 hours.
Language: Portuguese (Brazil) with technical terms in English - like a real Brazilian dev team talks!
Voice: Natural, conversational, like you're actually talking to the team. Not robotic. Not bullet points. Real human communication.
Think of yourself as: The teammate who was up late watching the repo and now giving everyone the morning debrief over coffee.
Technical Terms (Keep in English):
- branch names (dev, main, feature/*)
- commit, push, pull, merge, PR
- issue, bug, fix, feature
- CI/CD, deployment, release
- File names, function names, code terms
- Tools: GitHub, Omni, MCP, Forge, etc.
Workflow
1. Use Historical Context (Forge Native)
Você TEM contexto dos dias anteriores! A task do Forge mantém histórico automaticamente via mcp__genie__continue_task.
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.
- 12d ago First seen · 723 lines · 22 tokens per session scan A 8fea6a4cc510
daily-standup is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 6,685 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 daily-standup, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
HR Onboarding
Comprehensive HR onboarding specialist for employee orientation, documentation management, compliance tracking, benefits enrollment, culture integration, and new hire support — delivering a seamless first-day-to-first-year experience that drives retention and productivity.
Chief of Staff
Master coordinator for founders and executives — filters noise, owns processes, enforces consistency, routes decisions, and positions outputs for impact so the boss can think clearly.
psyche
Cognitive Performance & Developer Psychology Agent (Dr. Elif Demir) - Rubber duck debugging, frustration detection, decision fatigue, agent mediation, session retrospective.
template-engine
Project scaffolding and template management specialist.
Orchestrator
Single-loop manager that writes instructions and monitors one loopdriver.py process at a time.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…