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-logsgit 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-logs)<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-logs"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-logs.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.00006 | $0.00752 |
| Opus 5 | $0.00003 | $0.00376 |
| Sonnet 5 | $0.00001 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
schedule-logs 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
View Execution Logs
Display execution history and logs for scheduled tasks.
Usage
/schedule logs [task-id-or-name] [options]
Process
-
Determine Scope
- If task specified: show logs for that task
- If no task: show recent logs across all tasks
-
Load History
- Read execution records from task config
- Read log files from
~/.claude/logs/
-
Format Output
- Show execution history table
- Optionally show detailed output
Output Formats
All Tasks (default)
# Recent Executions
| Time | Task | Status | Duration | Trigger |
|-------------------|-------------------|--------|----------|-----------|
| Jan 5 9:00 AM | Daily Code Review | OK | 45s | scheduled |
| Jan 5 6:00 PM | Backup Reminder | OK | 12s | scheduled |
| Jan 4 9:00 AM | Daily Code Review | OK | 38s | scheduled |
| Jan 4 10:00 AM | Weekly Audit | FAIL | 120s | manual |
Showing last 10 executions. Use `/schedule logs --limit 50` for more.
Specific Task
/schedule logs daily-review
# Execution History: Daily Code Review
**Task ID:** a1b2c3d4-...
**Schedule:** Weekdays at 9:00 AM
**Log file:** ~/.claude/logs/a1b2c3d4.log
## Recent Executions
| Time | Status | Duration | Trigger |
|-------------------|--------|----------|-----------|
| Jan 5 9:00 AM | OK | 45s | scheduled |
| Jan 4 9:00 AM | OK | 38s | scheduled |
| Jan 3 9:00 AM | OK | 42s | scheduled |
| Jan 2 9:00 AM | FAIL | 5s | scheduled |
| Jan 1 9:00 AM | OK | 40s | manual |
## Last Execution Output
[Jan 5 9:00 AM - Success]
Reviewing commits from yesterday...
Found 3 commits to review.
...
Detailed Output
/schedule logs daily-review --full
[Shows complete output from last execution]
Options
--limit N- Show last N executions (default: 10)--full- Show complete output from last execution--status <ok|fail>- Filter by status--since <date>- Show executions since date
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 · 107 lines · 6 tokens per session scan A 5cc914254cc2
schedule-logs is a command published in the GitHub repository jshchnz/claude-code-scheduler (510 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 752 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.