Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jshchnz/claude-code-scheduler/plugin install 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-history)<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-history"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-history/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jshchnz/claude-code-scheduler/schedule-history"><img src="https://agentmods.dev/badge/commands/jshchnz/claude-code-scheduler/schedule-history.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.01368 |
| Opus 5 | $0.00005 | $0.00684 |
| Sonnet 5 | $0.00002 | $0.00274 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade B, and why
schedule-history scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/logs/once.file-listing-e3df455d.log How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution History
View recent task executions across all projects. Interactive by default - select an execution to see the full log.
Usage
/scheduler:schedule-history [options]
Process
-
Scan Log Files
List all log files in
~/.claude/logs/:ls -la ~/.claude/logs/*.log 2>/dev/nullFor each
.logfile:- Get modification time (= last execution time)
- Check for corresponding
.error.logfile - Determine status: error log with content = failure, otherwise success
-
Get Task Metadata (optional)
For each task, try to read plist for project path:
cat ~/Library/LaunchAgents/com.claude.schedule.<task-id>.plist 2>/dev/nullExtract
WorkingDirectoryfor project path. -
Display Interactive List
Show numbered list sorted by most recent first:
EXECUTION HISTORY # TIME TASK ID PROJECT STATUS ───────────────────────────────────────────────────────────────────────────────── 1 5 min ago once.file-listing-e3df455d ~/Documents/GitHub OK 2 11 hours ago loc-review-joshing ~/Documents/GitHub FAIL Select a number to view full log, or press Enter to exit: -
On Selection - Show Full Log
When user selects a number (e.g., "1"):
cat ~/.claude/logs/once.file-listing-e3df455d.logIf there's an error log:
cat ~/.claude/logs/<task-id>.error.log -
Show Actions After Log
───────────────────────────────────────────────────────────────────────────────── [E] View error log [R] Re-run task [B] Back to list [Q] Quit
Output Format
List View
╭─────────────────────────────────────────────────────────────────────────────╮
│ EXECUTION HISTORY │
╰─────────────────────────────────────────────────────────────────────────────╯
# TIME TASK ID PROJECT STATUS
─────────────────────────────────────────────────────────────────────────────
1 5 minutes ago once.file-listing-e3df455d ~/Documents/GitHub ✓ OK
2 11 hours ago loc-review-joshing ~/Documents/GitHub ✗ FAIL
─────────────────────────────────────────────────────────────────────────────
2 executions found │ 1 succeeded │ 1 failed
Select a number (1-2) to view full 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.
- 8d ago First seen · 181 lines · 10 tokens per session scan B 245e670fd6d4
schedule-history is a command published in the GitHub repository jshchnz/claude-code-scheduler (510 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 1,368 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.