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_viewnpx skills add cvander/Maya --skill schedule_viewgit 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.00010 | $0.00299 |
| Opus 5 | $0.00005 | $0.00150 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
schedule-view 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 View
Display the current weekly staff schedule with shift details and hours summary.
When to Use
- When Maya or staff need to see the current week's schedule
- When checking total hours per staff member
- Before making scheduling decisions
Procedure
python -m skills.schedule_view --format json
python -m skills.schedule_view --format json --week-of 2026-04-13
python -m skills.schedule_view --format json --schedule-dir docs/schedule
Exit Codes
| Code | Meaning |
|---|---|
| 0 | OK |
| 1 | Warnings/findings present |
| 2 | Config error |
| 3 | Data error |
| 10 | Unexpected error |
Verification
- Exit code is 0 or 1
- stdout is valid JSON (with --format json)
data.entriescontains parsed schedule rowsdata.staff_hourscontains per-staff hour totals
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 399 B runs code
- fixtures/FIXTURES.md 207 B
- fixtures/happy_path/current.md 372 B
- fixtures/happy_path/expected.json 943 B
- fixtures/warn_case/current.md 114 B
- fixtures/warn_case/expected.json 216 B
- main.py 4.1 KB runs code
- manifest.toml 282 B
- test_main.py 3.1 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 · 53 lines · 10 tokens per session scan A 50390f780114
schedule-view is a skill published in the GitHub repository cvander/Maya (10 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 299 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
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…