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/openapi/openapi-skills/openapi-invoicingnpx skills add openapi/openapi-skills --skill openapi-invoicinggit clone --depth 1 https://github.com/openapi/openapi-skillsWhat 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.00072 | $0.00674 |
| Opus 5 | $0.00036 | $0.00337 |
| Sonnet 5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
openapi-invoicing 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Openapi invoicing & payments
Bearer token required (see the openapi-auth skill). Sending invoices/receipts to the Revenue Agency and paying bills are irreversible fiscal/financial actions — always confirm with the user first.
Invoice (preferred) — https://invoice.openapi.com
Full management of Italian electronic invoices (FatturaPA XML) and digital receipts.
POST /IT-invoices— create/send an invoice to the SDI;GET /IT-invoices,GET /IT-invoices/{id}— list and monitor states (delivery, rejection)POST /IT-invoices_import— import externally created invoicesPOST|GET|PATCH|DELETE /IT-configurations[/{fiscal_id}]— per-company configuration (signature, legal storage,receipts_authentication)POST /IT-receipts— send a digital receipt;GET|PATCH|DELETE /IT-receipts/{id}(PATCH returns items from a receipt)
Key constraints:
- Receiving supplier invoices requires registering Openapi's Recipient Code on the Revenue Agency website: code PIC7CPS (Invoice API).
- Receipts cannot be sent 23:55–00:00 Italian time (queued to the next day); the receipt service requires enabling third-party credentials on the Agenzia delle Entrate portal (guide: https://docs.openapi.it/Procedura-manuale-per-incarico.pdf). Freelancers/sole proprietorships cannot delegate and must use their own credentials.
SDI (lower-level) — https://sdi.openapi.it
POST /business_registry_configurations(fiscal_id + email; legal-storage registration email follows)POST /api_configurations— set callbacks for notificationsPOST /invoices— send XML invoice; variants/invoices_signature,/invoices_legal_storage,/invoices_signature_legal_storageGET /invoices/{uuid},GET /invoices_download/{uuid},GET /invoices_notifications/{uuid}- Imports:
POST /customer_invoice_imports,POST /supplier_invoice_imports(+_legal_storagevariants); test withPOST /simulate/{type}
Recipient Code for SDI API: JKKZDGR. If the wallet runs dry the configuration is suspended — reactivate with PATCH /business_registry_configurations/{fiscal_id}/activate after recharging. PA invoices are auto-detected and signed.
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.
- 3d ago First seen · 38 lines · 72 tokens per session scan A d9a00ea6dc06
openapi-invoicing is a skill published in the GitHub repository openapi/openapi-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 674 once invoked, about $0.0004 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-30.
Other skills, from other repositories
robinhood-cli
Use this skill when the user asks to inspect, research, plan, or operate a Robinhood account through the repository's CLI, MCP server, or importable API. It routes account reads, portfolio analysis, equities, options, orders, watchlists, recurring investments, settings, tax lots, tax documents, tax-mechanics research…
verify-polish-company
Verify Polish companies and contractors by NIP, KRS, or REGON; check VAT status and bank accounts against the Ministry of Finance White List (Biała Lista); look up REGON/GUS registry data (including sole traders / JDG); read KRS registry data; and validate EU VAT numbers via VIES. Uses skanfirmy.pl's free, public API…
kyc-doc-parse
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
query-address-info
Snapshot of a single wallet's token holdings on a specific chain — list of every token currently held with name, symbol, current price, 24h price change, and holding quantity. Use when the user provides an explicit wallet address (or says "my wallet") and wants the current portfolio: "what does 0x... hold", "wallet…
openapi-glossary
Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.
scalar-docs
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.