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-listgit 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-list)<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-list"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-list.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.00014 | $0.01185 |
| Opus 5 | $0.00007 | $0.00593 |
| Sonnet 5 | $0.00003 | $0.00237 |
| Haiku 4.5 | $0.00001 | $0.00119 |
Grade A, and why
schedule-list 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 4d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Scheduled Tasks
Display ALL scheduled tasks across all projects by scanning the native scheduler.
Process
-
Discover ALL Registered Tasks from Native Scheduler
macOS (launchd):
ls ~/Library/LaunchAgents/com.claude.schedule.*.plist 2>/dev/nullFor each plist found, extract task info:
plutil -p ~/Library/LaunchAgents/com.claude.schedule.<id>.plistLinux (crontab):
crontab -l | grep "# claude-scheduler:"Windows:
schtasks /Query /FO CSV | findstr "ClaudeScheduler" -
Parse Task Information From each native scheduler entry, extract:
- ID: From filename/label (e.g.,
com.claude.schedule.loc-review-joshing→loc-review-joshing) - Type: Detect from filename:
com.claude.schedule.once.<id>.plist→ one-timecom.claude.schedule.<id>.plist→ recurring
- Project: From
WorkingDirectoryin plist - Schedule:
- Recurring: From
StartCalendarInterval→ pattern like "Daily at X" - One-time: Extract
TARGET=<timestamp>from ProgramArguments, convert withdate -r <timestamp>
- Recurring: From
- Command: From
ProgramArguments
For one-time tasks, extract target timestamp from bash command:
# ProgramArguments contains: "TARGET=1736376240; NOW=..." # Extract and convert: date -r 1736376240 "+%b %d, %Y %I:%M %p" - ID: From filename/label (e.g.,
-
Enrich with Config Metadata (optional)
- If the task's
WorkingDirectoryhas a.claude/schedules.json, read it for name/description - Fall back to ID as name if config not found
- If the task's
-
Check Status
launchctl list | grep com.claude.schedule- Status
0= enabled and healthy - Status
-= loaded but never run
- Status
-
Display Table Format output as a table with columns:
- ID (unique task identifier for use with other commands)
- Type (one-time / recurring)
- Project (working directory path, shortened with ~)
- Schedule (human-readable: exact date for one-time, pattern for recurring)
- Status (enabled/pending for one-time, enabled/disabled for recurring)
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.
- 4d ago First seen · 144 lines · 14 tokens per session scan A e666f678630b
schedule-list is a command published in the GitHub repository jshchnz/claude-code-scheduler (510 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 1,185 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-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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.