Borrowing it
Nothing to install: this file belongs to walm00/business-context-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/walm00/business-context-os/main/.claude/skills/schedule-tune/SKILL.mdgit clone --depth 1 https://github.com/walm00/business-context-osWrote 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/walm00/business-context-os/schedule-tune)<a href="https://agentmods.dev/skills/walm00/business-context-os/schedule-tune"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/schedule-tune/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/walm00/business-context-os/schedule-tune"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/schedule-tune.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.00241 | $0.03014 |
| Opus 5.5 | $0.00096 | $0.01206 |
| Sonnet 5.5 | $0.00048 | $0.00603 |
| Haiku 4.5 | $0.00024 | $0.00301 |
Grade A, and why
schedule-tune 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule Tune
Purpose
Claude edits schedule-config.json on the user's behalf. Regular users shouldn't be editing JSON with specific schema rules — they describe what they want, Claude does the translation.
The skill is defensive: it validates every change, shows the exact before/after diff, and refuses to write anything malformed. If the user's intent is ambiguous, it asks a clarifying question rather than guessing.
Preconditions
.claude/quality/schedule-config.jsonmust exist. If it does not, stop and say: "No schedule config found. If you haven't set up BCOS scheduling yet, runcontext-onboardingStep 6. If you think config should exist, check you're in the right repo."- The file must parse as JSON. If malformed, stop and say: "schedule-config.json is malformed. I can repair it from the template — want me to reset it to defaults?" — if yes, copy from
.claude/quality/schedule-config.template.json, strip_comment/_aboutfields, write.
Supported intents
Recognise the user utterance and map to a structured edit.
1. Change a job's schedule
Utterances: "run audit twice a week", "change daydream to every 3 days", "switch architecture review to quarterly", "run index-health on weekdays only", "audit on Tuesdays and Fridays"
Edit: jobs.{job}.schedule = <new value>
Value resolution:
- Simple weekday → use shortcut (
"mon","tue"etc.) - "daily" / "every day" →
"daily" - "weekdays" / "Monday through Friday" →
"weekdays" - "weekly" alone → ambiguous, ask which day (default offered: current value if it's already a single weekday, else Monday)
- "twice a week" → ask which days (offer Tue+Fri default), resolve to
"tue,fri"shorthand (if config supports comma-separated) or raw cron"0 9 * * 2,5" - "N times a week" with N>2 → offer specific day set
- "every N days" / "every other day" →
"every-{N}d" - "monthly" →
"1st"(default 1st of month) - "quarterly" → raw cron
"0 9 1 */3 *"(first of every 3rd month) - "never" / "off" / "disable this" →
"off"OR setenabled: false— ask user which they mean. Disabling viaenabled: falsekeeps config;"off"in schedule also works but is less intuitive. Default toenabled: falseunless user insists on schedule-based off. - Raw cron string — accept as-is after validation
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 · 276 lines · 241 tokens per session scan A 41b7baf44a17
schedule-tune is a skill published in the GitHub repository walm00/business-context-os (22 stars, last pushed 5mo ago), licensed MIT. It adds 241 tokens to every session and 3,014 once invoked, about $0.0010 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
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, list, or version-gated kanban views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-query
Answer an explicitly vault-scoped question from an Obsidian wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the wiki. Do not route ordinary…