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-removegit 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-remove)<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-remove"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-remove.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.00008 | $0.00504 |
| Opus 5 | $0.00004 | $0.00252 |
| Sonnet 5 | $0.00002 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
schedule-remove 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 3d 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
Remove Scheduled Task
Remove a task from the schedule configuration and unregister from the native scheduler.
Usage
/schedule remove <task-id-or-name>
Process
-
Find Task
- Search by exact ID match first
- Then search by name (case-insensitive)
- Check both project and global configs
-
Confirm Removal
- Show task details before removing
- Ask for confirmation: "Remove task 'Daily Code Review'? (y/n)"
-
Remove Task
- Unregister from native scheduler (launchd/cron/schtasks)
- Remove from schedules.json
- Optionally delete log files
-
Confirm Success
- Show confirmation message
- Remind about
/schedule listto verify
Example Interaction
User: /schedule remove daily-review
Claude: Found task:
- Name: Daily Code Review
- ID: a1b2c3d4-...
- Schedule: Weekdays at 9:00 AM
- Scope: project
Are you sure you want to remove this task? (y/n)
> y
Task "Daily Code Review" has been removed.
- Unregistered from launchd
- Removed from .claude/schedules.json
Run /schedule list to verify.
Error Handling
Task not found:
Task "xyz" not found.
Available tasks:
- daily-review (Daily Code Review)
- weekly-audit (Weekly Dependency Audit)
Try: /schedule remove daily-review
Multiple matches:
Multiple tasks match "review":
1. daily-review - Daily Code Review (project)
2. pr-review - PR Review Reminder (global)
Please specify the exact task ID:
/schedule remove daily-review
Options
If the user passes arguments:
$ARGUMENTScontains the task ID or name- If no argument, show
/schedule listfirst and ask which to remove
Cleanup
Optionally ask if they want to delete associated log files:
Delete log files for this task? (y/n)
> n
Log files preserved at ~/.claude/logs/a1b2c3d4.log
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.
- 3d ago First seen · 95 lines · 8 tokens per session scan A 0de807c80971
schedule-remove is a command published in the GitHub repository jshchnz/claude-code-scheduler (510 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 504 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
git
Git operations with intelligent commit messages and workflow optimization.
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.