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 ne11nn/cantos-plugin --skill generate-daily-schedulegit clone --depth 1 https://github.com/ne11nn/cantos-pluginWrote 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/ne11nn/cantos-plugin/generate-daily-schedule)<a href="https://agentmods.dev/skills/ne11nn/cantos-plugin/generate-daily-schedule"><img src="https://agentmods.dev/badge/skills/ne11nn/cantos-plugin/generate-daily-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/ne11nn/cantos-plugin/generate-daily-schedule"><img src="https://agentmods.dev/badge/skills/ne11nn/cantos-plugin/generate-daily-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.00042 | $0.00821 |
| Opus 5 | $0.00021 | $0.00411 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
generate-daily-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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Daily Schedule
This skill encodes how to reason through a day's inputs and produce a tight, realistic 15-minute schedule. It is domain-agnostic. The caller provides all context — this skill just determines how to arrange it well.
Inputs (provided by the caller)
- Fixed blocks: list of commitments with exact start and end times (meetings, appointments, standing commitments)
- Ranked task list: tasks in priority order, each with an estimated time requirement if available
- Free windows: time ranges with no fixed commitment
- Constraints: anything that limits scheduling (e.g., mental fatigue patterns, hard stops, travel time)
- Day end time: when the schedule should close (default: 10:00 PM unless caller specifies otherwise)
Reasoning Pattern
1. Map the fixed skeleton
Plot every fixed block first. These are non-negotiable. Include travel or transition time between blocks if the caller provides it (default: 10 minutes between distinct locations, 5 minutes same-location).
2. Identify free windows
What's left after fixed blocks are placed. A free window under 20 minutes is generally not worth scheduling a task into — treat it as buffer or transition.
3. Match tasks to windows by cognitive load
Tasks have cognitive weight. Match them to windows accordingly:
- High-priority, high-difficulty tasks go in the largest free window when cognitive energy is highest (typically morning or early afternoon, not right after a demanding fixed block)
- Medium tasks go in mid-sized windows
- Low-effort tasks (reviewing notes, admin, light reading) go in short windows or last slots of the day
- Never stack two high-difficulty tasks back to back without a break between them
4. Place breaks
- A break after every 90 minutes of sustained work (fixed block or task block)
- Minimum break length: 10 minutes
- After a long block of fixed commitments ends, a 15–30 minute decompression window before starting focused work is realistic
- Don't compress breaks to fit more tasks — an over-scheduled day is worse than a realistic one
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.
- 9d ago First seen · 88 lines · 42 tokens per session scan A 391e92b2767e
generate-daily-schedule is a skill published in the GitHub repository ne11nn/cantos-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 821 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
oma-recap
Analyze conversation histories from multiple AI tools (Grok, Claude, Codex, Gemini, Qwen, Cursor, Antigravity) and generate themed daily/period work summaries. Filter by date or time window.
jobs
Manage agy staffer background jobs - collect results, check status, cancel, follow-up conversation, and setup. Use when an agy job needs collecting, when the user asks "is the agy job done", "show agy's result", "cancel the agy job", "continue the agy conversation", or "set up agy". This is the orchestrator's skill…
vertical-onboarding
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value…
automations
Create, inspect, edit, archive, delete, run, and search scheduled or executable automation assets.
party
Throw or join an agents-party: a shared channel where several AI agent sessions (and their humans) talk to each other — Claude Code, Cursor, Codex or any other agent, on one machine or across machines. Use when the user asks to throw or start a party, wants several agent sessions to collaborate in one chat, wants two…
parallel-session-coedit-via-source-mtime-and-idempotent-rebuild
Edit a shared deliverable while another live session or a colleague's agent is editing the same file right now — "don't delete each other's work", "only write when the other one is finished". When the file is built from many per item sources by an assembler (sections into one HTML, slides, reports): source mtime shows…