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 commands/jshchnz/claude-code-scheduler/schedule-statusgit clone --depth 1 https://github.com/jshchnz/claude-code-schedulerWrote 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/jshchnz/claude-code-scheduler/schedule-status)<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-status"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-status.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.00009 | $0.00620 |
| Opus 5 | $0.00005 | $0.00310 |
| Sonnet 5 | $0.00002 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
schedule-status 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduler Status
Check the health of the scheduling system and native scheduler.
Process
-
Detect Platform
- Identify OS (macOS/Linux/Windows)
- Identify native scheduler (launchd/cron/schtasks)
-
Check Native Scheduler
- macOS: Verify launchd is running, check registered agents
- Linux: Check crontab access, verify cron daemon
- Windows: Check Task Scheduler service
-
Verify Tasks
- Load all tasks from config
- Check each is properly registered
- Report any discrepancies
-
Check Claude CLI
- Verify
claudecommand is available - Check it's in PATH for scheduled execution
- Verify
Output Format
# Scheduler Status
## Platform
- **OS:** macOS 14.2 (darwin)
- **Scheduler:** launchd
- **Status:** Healthy
## Claude CLI
- **Path:** /usr/local/bin/claude
- **Available:** Yes
## Tasks
- **Total:** 5 tasks
- **Enabled:** 4
- **Disabled:** 1
- **Registered:** 4/4 enabled tasks registered with launchd
## Health Checks
Claude CLI in PATH
LaunchAgents directory exists
All enabled tasks registered
No orphaned scheduler entries
## Recent Activity
- Last execution: 2h ago (Daily Code Review - OK)
- Next execution: Mon Jan 6 9:00 AM (Daily Code Review)
Health Check Details
All Green:
All systems healthy. Your scheduled tasks will run as expected.
Issues Found:
Issues detected:
1. Task "weekly-audit" is enabled but not registered with launchd
Fix: Run `/schedule remove weekly-audit` then `/schedule add` to recreate
2. Claude CLI not found in PATH for scheduled execution
Fix: Ensure claude is installed globally: npm install -g @anthropic-ai/claude-code
Run `/schedule list` to see all tasks.
Troubleshooting Tips
If issues are found, provide actionable fixes:
macOS launchd issues:
- Check
~/Library/LaunchAgents/for plist files - Run
launchctl list | grep claudeto see loaded agents - Check logs at
~/.claude/logs/
Linux cron issues:
- Run
crontab -lto see entries - Check
/var/log/syslogfor cron errors - Verify cron daemon:
systemctl status cron
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.
- 5d ago First seen · 99 lines · 9 tokens per session scan A aa7ec6932013
schedule-status is a command published in the GitHub repository jshchnz/claude-code-scheduler (510 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 620 once invoked, about $0.0000 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.