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 skills/breadchaincoop/labor.fun/scheduling-rulesnpx skills add BreadchainCoop/labor.fun --skill scheduling-rulesgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWhat 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 | $0.00041 | $0.00989 |
| Opus 5 | $0.00020 | $0.00495 |
| Sonnet 5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
scheduling-rules 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 2d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scheduling-rules — Task Scheduling Reference
How Breadbrich Engels schedules and manages recurring/one-time tasks.
Task Types
| Type | schedule_type |
schedule_value |
Example |
|---|---|---|---|
| Cron | cron |
Cron expression (local time) | 0 9 * * 1 (Mon 9am ET) |
| Interval | interval |
Milliseconds | 3600000 (every hour) |
| One-time | once |
ISO timestamp (local, NO Z suffix) | 2026-05-07T14:00:00 |
⚠️ CRITICAL GOTCHA: Timezone Handling
- Cron: Uses LOCAL timezone (ET).
0 9 * * *= 9 AM ET. ✓ - Once: Also local time. Use
2026-05-07T14:00:00(NOZsuffix). ✓ - Before sending any time-sensitive message: Verify current time if the task involves telling someone what time something is.
Script Gates
For recurring tasks, add a script to avoid unnecessary agent wake-ups:
{
"script": "bash -c '...'",
"prompt": "Do the thing",
"schedule_type": "cron",
"schedule_value": "0 9 * * *"
}
Script prints JSON: { "wakeAgent": true/false, "data": {...} }
wakeAgent: false→ agent sleeps, waits for next runwakeAgent: true→ agent wakes with data + prompt
Always test scripts first in the sandbox before scheduling.
API Credit Conservation
Each wake-up uses API credits. For tasks > 2x/day:
- Suggest a script gate
- Help find minimum viable frequency
- For LLM evaluation, suggest direct API calls in the script
Context Modes
| Mode | Use When |
|---|---|
group |
Task needs chat history / conversation context |
isolated |
Self-contained task, all context in prompt |
Delivery Mode (privacy) — prevents reminder leaks
delivery controls whether the task's result narration is posted to the bound chat.
| Mode | Use When |
|---|---|
channel (default) |
The result is meant for everyone in the chat — daily briefings, in-channel reminders, public status posts. |
silent |
Private reminders / DM-only tasks. The result is NOT posted to any channel; the real output goes out via dm_user to the requester. |
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.
- 2d ago First seen · 104 lines · 41 tokens per session scan A 3ce1d0271ac2
scheduling-rules is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 989 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…