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/cvander/maya/schedule_notifynpx skills add cvander/Maya --skill schedule_notifygit clone --depth 1 https://github.com/cvander/MayaWhat 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.00014 | $0.00305 |
| Opus 5 | $0.00007 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
schedule-notify 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.
What it actually says
Schedule Notify
Parse schedule JSON output (from schedule-view or schedule-draft) and generate per-staff notification messages ready to copy-paste.
When to Use
- After generating a schedule with schedule-view or schedule-draft
- When staff need to be notified of their upcoming shifts
- Before publishing a finalized schedule
Procedure
python -m skills.schedule_view --format json > /tmp/schedule.json
python -m skills.schedule_notify --format json --input-file /tmp/schedule.json
Exit Codes
| Code | Meaning |
|---|---|
| 0 | OK, notifications generated |
| 1 | Warnings (no shifts found) |
| 2 | Config error |
| 3 | Data error (missing or invalid input file) |
| 10 | Unexpected error |
Verification
- Exit code is 0
- stdout is valid JSON (with --format json)
data.notificationscontains one entry per staff member- Each notification has
staff,shift_count,total_hours, andmessagefields
What ships with it
10 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.
- __init__.py 0 B runs code
- __main__.py 341 B runs code
- fixtures/FIXTURES.md 207 B
- fixtures/happy_path/expected.json 803 B
- fixtures/happy_path/input.json 679 B
- fixtures/warn_case/expected.json 177 B
- fixtures/warn_case/input.json 113 B
- main.py 4.0 KB runs code
- manifest.toml 281 B
- test_main.py 3.6 KB runs code
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 · 49 lines · 14 tokens per session scan A ece624c2bcd0
schedule-notify is a skill published in the GitHub repository cvander/Maya (10 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 305 once invoked, about $0.0001 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.