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-rungit 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-run)<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-run"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-run.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.00007 | $0.00447 |
| Opus 5 | $0.00003 | $0.00224 |
| Sonnet 5 | $0.00001 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
schedule-run 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.
What it actually says
Run Scheduled Task
Execute a scheduled task immediately, bypassing its schedule trigger.
Usage
/schedule run <task-id-or-name>
Process
-
Find Task
- Search by ID or name
- Load task configuration
-
Confirm Execution
- Show task details
- Ask for confirmation (optional, can skip with --yes flag)
-
Execute Task
- Run the configured command
- Stream output to user
- Record execution in history
-
Report Results
- Show execution status (success/failure)
- Show duration
- Show any output or errors
Example Interaction
User: /schedule run daily-review
Claude: Running task: Daily Code Review
Command: /review-code --scope=yesterday
Working directory: /Users/home/projects/myapp
[Executing...]
--- Task Output ---
Reviewing commits from yesterday...
Found 3 commits to review.
Commit abc123: Add user authentication
- Good: Proper input validation
- Suggestion: Consider rate limiting
...
--- End Output ---
Task completed successfully in 45 seconds.
Options
Via $ARGUMENTS:
- Task ID or name (required)
Error Handling
Task not found:
Task "xyz" not found.
Run /schedule list to see available tasks.
Task disabled:
Task "weekly-audit" is currently disabled.
Would you like to run it anyway? (y/n)
> y
Execution failure:
Task failed with exit code 1.
Error output:
Error: Could not connect to repository
Check the full log at: ~/.claude/logs/a1b2c3d4.log
Execution Recording
After running, update the task's execution history:
- Record start/end time
- Record status (success/failure/timeout)
- Record triggered by "manual"
- Truncate and store output
This history is visible in /schedule logs.
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 · 104 lines · 7 tokens per session scan A 654a177b86ae
schedule-run is a command published in the GitHub repository jshchnz/claude-code-scheduler (510 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 447 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.
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.