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/inventory_checknpx skills add cvander/Maya --skill inventory_checkgit 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.00493 |
| Opus 5 | $0.00007 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
inventory-check 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
Inventory Check
Reads beer.md, spirits.md, and wine.md from the inventory directory. Compares each item's quantity against its reorder threshold. Reports items at or below threshold.
Read-only. Does not modify files or reach external services. No PII in output.
When to Use
- Daily morning check before opening (scheduled: 10:00 AM)
- Before placing vendor orders (Sunday/Monday)
- When a bartender reports running low on something
- After receiving a delivery, to confirm stock levels updated
Procedure
Run the skill from the repo root:
# Human-readable summary
python -m skills.inventory_check
# Structured JSON output (for automation)
python -m skills.inventory_check --format json
# Against a custom inventory directory
python -m skills.inventory_check --inventory-dir path/to/inventory --format json
Parse the JSON result:
status: "ok" (nothing to reorder) or "warn" (items need attention)findings: array of LOW_STOCK items with category, item name, qty, reorder_atdata.items_scanned: total items checkeddata.low_stock: detailed list of low items
Exit Codes
| Code | Meaning |
|---|---|
| 0 | All stock levels acceptable |
| 1 | One or more items at or below reorder threshold |
| 2 | Config error (bad arguments) |
| 3 | Data error (can't read inventory files) |
| 10 | Unexpected error |
Verification
After running, confirm:
- Exit code is 0 or 1 (not 2, 3, or 10)
- stdout is valid JSON (when using --format json)
data.items_scanned> 0 (files were actually read)- If exit code is 1,
findingsarray is non-empty
What ships with it
13 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 74 B runs code
- __main__.py 178 B runs code
- fixtures/FIXTURES.md 136 B
- fixtures/happy_path/beer.md 288 B
- fixtures/happy_path/expected.json 202 B
- fixtures/happy_path/spirits.md 275 B
- fixtures/happy_path/wine.md 211 B
- fixtures/low_stock/beer.md 352 B
- fixtures/low_stock/expected.json 786 B
- fixtures/malformed/beer.md 196 B
- main.py 3.5 KB runs code
- manifest.toml 300 B
- test_main.py 7.0 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 · 70 lines · 14 tokens per session scan A 80245f20412f
inventory-check 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 493 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…