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 instructions/invoicexml/invoicexml-mcp/gemini-mdgit clone --depth 1 https://github.com/InvoiceXML/invoicexml-mcpWrote 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/instructions/invoicexml/invoicexml-mcp/gemini-md)<a href="https://agentmods.dev/instructions/invoicexml/invoicexml-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/invoicexml/invoicexml-mcp/gemini-md.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.01000 | $0.01000 |
| Opus 5 | $0.00500 | $0.00500 |
| Sonnet 5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
invoicexml-mcp GEMINI.md 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
InvoiceXML MCP Server
InvoiceXML turns structured invoice data into compliant electronic invoices, checks existing invoices against the EN 16931 standard, and converts between formats, all as native tools you can call directly. It covers UBL (Peppol BIS Billing 3.0), UN/CEFACT CII, German XRechnung, and the hybrid PDF formats Factur-X and ZUGFeRD.
Use these tools whenever a user needs to create, check, convert, read, or render a European e-invoice. You do not need to know the EN 16931 specification or run any validation yourself: call the right tool and surface its result.
Connecting
- Hosted (recommended):
https://mcp.invoicexml.com, fully managed, secured with OAuth 2.1 (the user signs in; no API key to paste). - Self-hosted: open source at
https://github.com/InvoiceXML/invoicexml-mcp, run on your own infrastructure with an InvoiceXML API key.
Free account and credits: https://www.invoicexml.com/account/signup.
Landing page: https://www.invoicexml.com/mcp-server.
Tools
| Tool | Use it when the user wants to... |
|---|---|
create_invoice |
Generate a compliant invoice (UBL, CII, XRechnung, Factur-X, or ZUGFeRD) from structured data. |
validate_xml_invoice |
Check a UBL / CII / XRechnung XML document against EN 16931 and Schematron. |
validate_pdf_invoice |
Check a Factur-X / ZUGFeRD hybrid PDF and the XML embedded inside it. |
render_invoice |
Turn UBL / CII / XRechnung XML into a clean, human-readable PDF preview. |
extract_invoice |
Pull the structured JSON or the embedded CII XML out of a hybrid PDF. |
embed_invoice |
Combine a PDF and a CII XML into a Factur-X / ZUGFeRD hybrid PDF. |
convert_invoice |
Convert between UBL, CII, XRechnung, Factur-X, and ZUGFeRD. |
Pick by document type: use validate_pdf_invoice / extract_invoice for hybrid
PDFs (Factur-X, ZUGFeRD), and validate_xml_invoice / render_invoice for plain
XML (UBL, CII, XRechnung). create_invoice consumes an API credit and produces a
new document, so it is the only tool that should require user approval; the others
are read-only or transform operations.
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 · 76 lines · 1,000 tokens per session scan A 76cbf2aa5dd2
invoicexml-mcp GEMINI.md is an instructions file published in the GitHub repository InvoiceXML/invoicexml-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,000 tokens to every session, about $0.0050 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 instructions, from other repositories
safe-docx AGENTS.md
Instructions for UseJunior/safe-docx, covering openspec instructions, ecma-376 conformance, workflow conventions, branch naming and commits.
safe-docx GEMINI.md
Instructions for UseJunior/safe-docx, covering safedocx — ai document editing (mcp server), trust boundary, available tools, reading and navigation and batch editing.
optionsahoy-mcp AGENTS.md
Instructions for AlvisoOculus/optionsahoy-mcp, covering agents.md, what this repo is, what an agent should do with this server, how an agent connects and required-input discipline.
optionsahoy-mcp GEMINI.md
Instructions for AlvisoOculus/optionsahoy-mcp, covering optionsahoy equity-compensation tools, tools and usage rules.
sumup-skills GEMINI.md
Instructions for sumup/sumup-skills: This extension provides guidance for building SumUp payment integrations.
gemini-extension GEMINI.md
Instructions for conversiontools/gemini-extension, covering conversion tools, if the tools are not available, how to convert a file, build a custom converter (ai studio) and tip: prefer the ctio cli when available.