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 skills add thtskaran/claude-skills --skill schedulegit clone --depth 1 https://github.com/thtskaran/claude-skillsWrote 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/skills/thtskaran/claude-skills/schedule)<a href="https://agentmods.dev/skills/thtskaran/claude-skills/schedule"><img src="https://agentmods.dev/badge/skills/thtskaran/claude-skills/schedule/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/skills/thtskaran/claude-skills/schedule"><img src="https://agentmods.dev/badge/skills/thtskaran/claude-skills/schedule.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.00018 | $0.00472 |
| Opus 5.5 | $0.00007 | $0.00189 |
| Sonnet 5.5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
schedule 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 1mo 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
You are creating a reusable shortcut from the current session. Follow these steps:
1. Analyze the session
Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective.
2. Draft a prompt
The prompt will be used for future autonomous runs — it must be entirely self-contained. Future runs will NOT have access to this session, so never reference "the current conversation," "the above," or any ephemeral context.
Include in the description:
- A clear objective statement (what to accomplish)
- Specific steps to execute
- Any relevant file paths, URLs, repositories, or tool names
- Expected output or success criteria
- Any constraints or preferences the user expressed
Write the description in second-person imperative ("Check the inbox…", "Run the test suite…"). Keep it concise but complete enough that another Claude session could execute it cold.
3. Choose a taskName
Pick a short, descriptive name in kebab-case (e.g. "daily-inbox-summary", "weekly-dep-audit", "format-pr-description").
4. Determine scheduling
Pick one:
- Recurring ("every morning", "weekdays at 5pm", "hourly") →
cronExpression - One-time with a specific moment ("remind me in 5 minutes", "tomorrow at 3pm", "next Friday") →
fireAtISO timestamp - Ad-hoc (no automatic run; user will trigger manually) → omit both
- Ambiguous → propose a schedule and ask the user to confirm before proceeding
cronExpression: Evaluated in the user's LOCAL timezone, not UTC. Use local times directly — e.g. "8am every Friday" → 0 8 * * 5.
fireAt: Compute the exact moment and emit a full ISO 8601 string with timezone offset, e.g. 2026-03-05T14:30:00-08:00. Never use cron for one-time tasks — cron has no one-shot semantics.
Finally, call the "create_scheduled_task" tool.
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.
- 1mo ago First seen · 41 lines · 18 tokens per session scan A a55c62f96260
schedule is a skill published in the GitHub repository thtskaran/claude-skills (22 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
playbook
Run a user-authored playbook from the vault: a multi-step guided procedure. Lists available global and local playbooks, selects one by trigger, and drives its steps in order — spawning per-step sub-agents or running inline, pausing at review gates.
vim-editing
A skill for learning and using Vim-style editing, including modal editing, movement commands, editing commands, counts, and modifiers. Vim is a keyboard-driven text editor with separate modes for moving and changing text.
dotfiles
A collection of personal configuration files for shells and command-line tools, often stored in a dotfiles repository and installed with symbolic links.
asking-good-questions
A guide to asking for help and clarifying questions, documented in Chinese.
shell-basics
A guide to using a command-line shell: moving through folders, finding programs, reading command help, handling paths and quotes, and using common text and file commands.
tmux
A terminal tool for arranging multiple panes and windows while keeping sessions alive after you disconnect.