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/svy04/ballast/schedulenpx skills add svy04/ballast --skill schedulegit clone --depth 1 https://github.com/svy04/ballastWrote 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/svy04/ballast/schedule)<a href="https://agentmods.dev/skills/svy04/ballast/schedule"><img src="https://agentmods.dev/badge/skills/svy04/ballast/schedule.svg" alt="Measured on agentmods" 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.00065 | $0.00861 |
| Opus 5 | $0.00032 | $0.00430 |
| Sonnet 5 | $0.00013 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
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 6d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule — events become entries, and nothing fires half-staged
The human fires the outward actions; the agent owns everything before that: noticing, entering, judging, preparing, recording. One file holds it: memory/SCHEDULE.md (create it on first use). Without a ledger, events are handled from memory — which means twice, or never.
Three kinds of entry
| Kind | What it is | Required fields |
|---|---|---|
| Fixed | dates known in advance — deadlines, eligibility days, submission windows | date · action · where the prepared material lives · what is still unconfirmed |
| Event | born outside — an outage, a model deprecation, a competitor incident | date it happened · freshness limit · judgment · prepared material · handling record |
| Bundle | deliverables that launch as one wave plan | member list · each member's staged / not staged · fire order on each channel's clock · the bundle rule |
The bundle rule: if one member is not staged, nothing fires. A half-launched wave reads as two small ones. Staging is all-or-nothing; firing is not all-at-once — every documented winning launch staged everything first, fired the channel with a ranking clock at its own hour, and released the rest in waves, because a same-minute blast on a ranked platform reads as vote manipulation. Verify the first member actually went live before the next wave fires.
The event procedure
- Notice — a scan (scheduled, or at session start) or the human's one line. The human is the fastest sensor; the scan is the floor, not the ceiling.
- Check the ledger first. An event already handled is never reacted to twice — that is what the handling record is for.
- Enter it with a freshness limit — a date after which the right reaction is no reaction, only a record.
- Judge it against red lines written in advance. An event can be an opportunity (people are moving), an avoid-day (your promotion lands as noise, or as bad taste on someone's crisis), or both at once — the same day can be right for joining conversations and wrong for self-promotion. Never attach a promotion to a tragedy. And watch the wounded party: if they reverse course within a day or two, the window closes and the right reaction becomes no reaction.
- Prepare everything the human needs to fire: the text, the destination, the timing, the one thing still unconfirmed.
- Report one line per changed entry. "No change" is a complete report.
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.
- 6d ago First seen · 44 lines · 65 tokens per session scan A 4a261ae6fc36
schedule is a skill published in the GitHub repository svy04/ballast (71 stars, last pushed 11d ago), licensed MIT. It adds 65 tokens to every session and 861 once invoked, about $0.0003 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-30.
Other skills, from other repositories
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.