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/cost_analysisnpx skills add cvander/Maya --skill cost_analysisgit 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.00309 |
| Opus 5 | $0.00007 | $0.00154 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
cost-analysis 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
Cost Analysis
Reads the current menu and inventory files to calculate pour cost per drink, category COGS, and margin percentages. Flags items with high pour costs (>30%) or low margins (<$8).
When to Use
- When reviewing menu pricing decisions
- Before adjusting prices on cocktails or spirits
- Monthly cost analysis for the bar
Procedure
python -m skills.cost_analysis --format json
python -m skills.cost_analysis --format json --category cocktails
Optional: --category all|beer|spirits|wine|cocktails (defaults to all).
Exit Codes
| Code | Meaning |
|---|---|
| 0 | OK, all margins healthy |
| 1 | Warnings: high pour cost or low margin items |
| 2 | Config error |
| 3 | Data error |
| 10 | Unexpected error |
Verification
- Exit code is 0 or 1
- stdout is valid JSON (with --format json)
data.itemscontains analyzed menu items with cost/margin data
What ships with it
11 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 90 B runs code
- __main__.py 502 B runs code
- fixtures/FIXTURES.md 392 B
- fixtures/happy_path/expected.json 2.0 KB
- fixtures/happy_path/inventory/spirits.md 553 B
- fixtures/happy_path/menu/current.md 524 B
- fixtures/warn_case/expected.json 1.6 KB
- fixtures/warn_case/menu/current.md 333 B
- main.py 11 KB runs code
- manifest.toml 314 B
- test_main.py 4.3 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 · 50 lines · 14 tokens per session scan A 3c336a6d7906
cost-analysis 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 309 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
connect-recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue…
stripe
Emulated Stripe API for local development and testing. Use when the user needs to process payments locally, test checkout flows, create customers, manage products and prices, handle payment intents, work with webhooks, or use the Stripe SDK without hitting real Stripe servers. Triggers include "Stripe API", "emulate…
create-payment-credential
Gets secure, one-time-use payment credentials (cards, tokens) from a Link wallet so agents can complete purchases on behalf of users. Use when the user says "get me a card", "buy something", "pay for X", "make a purchase", "I need to pay", "complete checkout", or asks to transact on any merchant site. Use when the…
stripe-best-practices
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatictax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment…
asc-ppp-pricing
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.
stripe-skill
Process payments, manage customers, issue refunds, and handle subscriptions via the Stripe CLI. Pass any Stripe command (customers, charges, paymentintents, refunds, invoices, products, prices, subscriptions) and the tool runs it for you and returns parsed JSON.