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 agents/automagik-dev/forge/daily-standupgit clone --depth 1 https://github.com/automagik-dev/forgeWrote 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/automagik-dev/forge/daily-standup)<a href="https://agentmods.dev/agents/automagik-dev/forge/daily-standup"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/daily-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.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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- daily-standup — 100% identical, 0 lines differ
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.
- 3d ago First seen · 723 lines · 22 tokens per session scan A 8fea6a4cc510
daily-standup is an agent published in the GitHub repository automagik-dev/forge (89 stars, last pushed 8mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
instruction-reflector
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
electron-app-debugger
Use this agent when you need to debug Electron application issues, particularly UI-related problems, component rendering issues, or when you need to bypass native dialogs for testing. This agent specializes in visual debugging through screenshots and color manipulation, and can programmatically control the app for…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
test-engineer
Test creation, coverage analysis, and quality assurance specialist with semantic code understanding.
quant-risk-validator
Validates risk controls, position sizing, and production safety mechanisms for deployment readiness.