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/schedule)<a href="https://agentmods.dev/commands/fatihkan/badi/schedule"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/schedule.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.00499 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
schedule 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
Scheduled command reminders. Shell-based reminder system for daily/weekly recurring tasks.
Required Tools
- Bash (badi schedule)
Procedure
Step 1: Existing Reminders
badi schedule list
Step 2: Add a New Reminder
# Every workday morning
badi schedule add "content start" --at "09:00" --days "mon-fri"
# Weekly (Sunday evening)
badi schedule add "content plan" --at "20:00" --days "sun"
# Daily
badi schedule add "wrap-up" --at "18:00" --days "daily"
Day ranges: pzt/sal/car/per/cum/cts/paz (TR) or mon/tue/wed/thu/fri/sat/sun (EN). Wrap-around supported: sat-sun, fri-mon.
Step 3: Shell Integration (first setup)
Add to ~/.zshrc or ~/.bashrc:
command -v badi &>/dev/null && badi schedule check 2>/dev/null
Shows due reminders at every shell start (60-minute tolerance).
Step 4: Removal
badi schedule list # See the IDs
badi schedule remove [id] # Remove
Step 5: Check
badi schedule check # Show what is due
Example Routines
# Workday mornings (09:00): content production session
badi schedule add "content start" --at "09:00" --days "mon-fri"
# Weekdays 18:00: end-of-day summary
badi schedule add "wrap-up" --at "18:00" --days "mon-fri"
# Weekly: Sunday evening content planning
badi schedule add "content plan" --at "20:00" --days "sun"
# Every Monday: weekly health
badi schedule add "health" --at "09:30" --days "mon"
# Start of each month: audit
badi schedule add "audit" --at "10:00" --days "mon"
Example Usage
/schedule list
/schedule add "content review" --at "16:00" --days "fri"
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 · 77 lines · 0 tokens per session scan A 59f26c59a9cc
schedule 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 499 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
catchup
Restore context after /clear by summarizing recent work and project state.
sessions
Browse Claude Code sessions history.
dashboard
Launch ccboard TUI dashboard.
ccboard-install
Install or update ccboard.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.