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/fatihkan/badiWrote 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/fatihkan/badi/standup)<a href="https://agentmods.dev/commands/fatihkan/badi/standup"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/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.1 | $0.00000 | $0.00348 |
| Opus 5 | $0.00000 | $0.00174 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
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 today.
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.
What it actually says
Daily standup command. Produces a quick status summary in under 30 seconds.
Required Tools
- Bash (git log)
- Read (task board, notes)
- Grep (activity scan)
Procedure (Target: 30 seconds)
Step 1: Git Activity (Parallel)
- Get the last working day's commits:
git log --oneline --since="yesterday" - Count the changed files
- Check the branch status
Step 2: Task Board (Parallel)
- Read the active tasks
- Count the completed ones
- Detect blocked tasks
- Identify newly added tasks
Step 3: Previous Notes (Parallel)
- Read the latest daily note
- Check the handoff note if one exists
- Find the "tomorrow's work" section
Step 4: Current Focus
- Determine today's priorities
- Check dependencies
- Any risks or blockers?
Output Format
=== BADI STANDUP ===
Date: [date]
YESTERDAY:
- [work done - from git commits and notes]
- [completed tasks]
TODAY:
- [planned work - in priority order]
- [in-progress tasks]
BLOCKERS:
- [blockers and expectations, if any]
- [otherwise: "No blockers, road clear."]
METRICS:
- Commits (yesterday): [count]
- Open Tasks: [count]
- Completed (yesterday): [count]
====================
Rules
- Keep it short and tight, 15 lines of output max
- One line per item
- Highlight blockers (if any)
- Always include the metrics
- Do not exceed 30 seconds
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.
- today First seen · 61 lines · 0 tokens per session scan A 986eda12c452
standup is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 348 tokens. 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.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.