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/close_outnpx skills add cvander/Maya --skill close_outgit 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.00015 | $0.00385 |
| Opus 5 | $0.00008 | $0.00192 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
close-out 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
Close-Out
Nightly cash reconciliation, tip split, and waste logging. Calculates variance between actual and expected revenue, splits tips 80/20 staff/house, and logs waste items. Writes a reconciliation report to data/close-out/.
When to Use
- At end of each shift or night to reconcile the register
- When Maya needs to log waste from the bar
- When tip splits need to be calculated and recorded
Procedure
python -m skills.close_out --format json \
--cash-count 850.00 \
--card-total 1200.00 \
--expected 2045.00 \
--tip-total 320.00 \
--waste-items "lime:5,beer:2"
Optional: --date YYYY-MM-DD (defaults to today), --data-dir PATH (defaults to data/close-out).
Exit Codes
| Code | Meaning |
|---|---|
| 0 | OK, variance within threshold |
| 1 | Warnings: cash over/short beyond $5 threshold |
| 2 | Config error |
| 3 | Data error |
| 10 | Unexpected error |
Verification
- Exit code is 0 or 1
- stdout is valid JSON (with --format json)
datafield contains variance, tip split, and waste items- Reconciliation file written to data/close-out/YYYY-MM-DD.md
What ships with it
8 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.
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 · 55 lines · 15 tokens per session scan A f42c37356ada
close-out is a skill published in the GitHub repository cvander/Maya (10 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 385 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.