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 bendrucker/claude --skill scheduledgit clone --depth 1 https://github.com/bendrucker/claudeWrote 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/bendrucker/claude/scheduled)<a href="https://agentmods.dev/skills/bendrucker/claude/scheduled"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/scheduled/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/bendrucker/claude/scheduled"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/scheduled.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.00047 | $0.00709 |
| Opus 5.5 | $0.00019 | $0.00284 |
| Sonnet 5.5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
scheduled 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduled
Reconcile this machine's launchd agents against descriptor directories committed under user/scheduled/<group>/, or declared out-of-repo for a machine whose task set is proprietary. One YAML descriptor per task, one directory per machine group.
Config
!cat ~/.config/claude-scheduled/config.json 2>/dev/null || echo CONFIG_MISSING
If the output above is CONFIG_MISSING and the requested mode is not setup, run references/setup.md first, then continue into the requested mode.
Mode
Requested mode: $0.
setup: read references/setup.mdsync: read references/sync.mdlist: runbun user/skills/scheduled/scripts/scheduled.ts list [dir...]and show the table (declared vs. installed, no launchd query)status: runbun user/skills/scheduled/scripts/scheduled.ts status [dir...]and show the table (adds launchd load state)run <label>: runbun user/skills/scheduled/scripts/scheduled.ts run <label>to kickstart an installed agent immediately, without waiting for its schedule- no argument: default to
status
Trailing arguments beyond the mode ($ARGUMENTS) pass through as dir... (group directories to scope the command to) or the label for run. Omitting directories reads every group from the config above.
Model
Each group is a directory of YAML descriptors, one task per file with fields label, schedule, mode, command, and an optional workdir, documented in user/scheduled/README.md. The directory name is the group. A machine's config declares which groups it manages, in-repo (user/scheduled/<group>, committed) or out-of-repo (~/.config/claude-scheduled/<group>, for a proprietary task set).
sync renders every headless descriptor to a launchd plist, installs anything new or changed, and prunes any me.bendrucker.claude.<group>.* agent no longer declared. The label prefix scopes every install and prune, so a group's sync never touches another group's agents or an unrelated com.user.* one.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 47 tokens per session scan A cd94cc28eb74
scheduled is a skill published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 709 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
ledger
OPS on-demand: This skill should be used when the user asks to "ops ledger", "what did we handle", or…
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…