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/wolfenazz/yzpzcode/invoicenpx skills add wolfenazz/YzPzCode --skill invoicegit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wolfenazz/yzpzcode/invoice)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/invoice"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/invoice.svg" alt="Measured on agentmods" height="20"></a>What 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.00046 | $0.00349 |
| Opus 5 | $0.00023 | $0.00175 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
invoice 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 yesterday.
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.
This is a copy
100% identical to invoice — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoice Skill
Produce a single-page printable invoice.
Workflow
- Read DESIGN.md.
- Layout:
- Top band: studio brand on the left, "INVOICE" + number + date + due date on the right.
- Two columns: From (sender) / Bill to (recipient) with addresses.
- Project ref + payment-terms strip.
- Line items table: description / qty / unit / amount.
- Right-aligned totals block: subtotal, retainer, tax, total due.
- Payment instructions (bank, wire, ACH).
- Thank-you note + signature line.
- Print stylesheet @media print to remove backgrounds.
Output contract
<artifact identifier="invoice-name" type="text/html" title="Invoice">
<!doctype html>...</artifact>
What ships with it
1 file 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.
- yesterday First seen · 49 lines · 46 tokens per session scan A 6c12ddb7b2b9
invoice is a skill published in the GitHub repository wolfenazz/YzPzCode (13 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 349 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to invoice, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
invoice-creator
Generate professional PDF invoices with line items, taxes, discounts, payment terms, and company branding.
product-data-cleanup
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.
product-spec-bulk-fetch
Extract structured FF&E specs from a list of product URLs into a schedule. Use to pull or bulk-import product-page data; not for PDF catalogs.
master-schedule
Initialize, validate, inspect, or import the current project's local FF&E product library. Use when a product workflow needs product-library.csv, when the user invokes /as:master-schedule, or when legacy master-schedule.json or canoa.json configuration is present.
offer-codes-setup
Generates offer code distribution strategies and configuration guides for subscription and IAP promotions — including partner campaigns, influencer programs, and email re-engagement. Use when setting up offer codes for distribution.
meeting-minutes-taker
Transforms raw meeting transcripts into high-fidelity, structured meeting minutes with iterative review for completeness. This skill should be used when (1) a meeting transcript is provided and meeting minutes, notes, or summaries are requested, (2) multiple versions of meeting minutes need to be merged without losing…