fintaro-belege-upload

fintaro-belege-upload is a skill for Claude Code, Codex from fintaro-ai/fintaro-mcp. It costs 76 tokens per session (780 once invoked), scanned A, original, Apache-2.0.

A skill for uploading a local invoice or receipt to Fintaro and checking that processing has started. It accepts PDF, PNG, JPEG, and WebP files up to 25 MB and requires the appropriate Fintaro permissions.

In plain words
What is it for?
Use it to upload a receipt or invoice, confirm its processing status, and inspect the returned basic invoice details.
Why use it?
It removes the need to perform the upload and immediate verification manually. It also reports when Fintaro identifies the file as a duplicate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to upload a receipt or invoice, confirm its processing status, and inspect the returned basic invoice details.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload
Install

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.

Any agent
npx skills add fintaro-ai/fintaro-mcp --skill fintaro-belege-upload
Clone the repo
git clone --depth 1 https://github.com/fintaro-ai/fintaro-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for fintaro-belege-upload

README.md
[![agentmods](https://agentmods.dev/badge/skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload/github.svg)](https://agentmods.dev/skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload)
Your own site
<a href="https://agentmods.dev/skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload"><img src="https://agentmods.dev/badge/skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for fintaro-belege-upload

Your own site · 80×15
<a href="https://agentmods.dev/skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload"><img src="https://agentmods.dev/badge/skills/fintaro-ai/fintaro-mcp/fintaro-belege-upload.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 780 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.00780
Opus 5 $0.00038 $0.00390
Sonnet 5 $0.00015 $0.00156
Haiku 4.5 $0.00008 $0.00078

Measured 11d ago against content hash 0dd03ec753ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

fintaro-belege-upload 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 11d 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.

skills/fintaro-belege-upload/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fintaro Belege-Upload

Lade eine lokale Beleg-Datei nach Fintaro hoch und bestätige, dass sie zur Verarbeitung angenommen wurde.

Voraussetzungen

  • Scope invoices:write (für den Upload) und invoices:read (zum Verifizieren).
  • Server eingebunden, whoami erfolgreich (siehe fintaro-onboarding).
  • Die Datei liegt lokal vor; Format PDF/PNG/JPEG/WebP, Größe ≤ 25 MB.

Vorgehen

  1. Scope bestätigen. Sicherstellen, dass der Key invoices:write hat (bei Unsicherheit whoami). Fehlt der Scope: abbrechen und den Nutzer bitten, einen Key mit invoices:write zu minten.

  2. Hochladen. Tool upload_invoice(file_path=<absoluter Pfad>) aufrufen. Rückgabe: { "invoice_id": <id>, "status": "processing", "deduplicated": <bool> }.

    • status ist direkt nach dem Upload immer processing — die Extraktion läuft asynchron im Hintergrund.
    • deduplicated: true bedeutet, dass Fintaro die Datei als Duplikat eines bereits vorhandenen Belegs erkannt hat; dann den Nutzer informieren.
  3. Verifizieren. Die zurückgegebene invoice_id über get_invoice(invoice_id) abrufen und die schmale Zusammenfassung zeigen (status, seller_name, invoice_number, invoice_date, amount_gross, currency). Solange die Extraktion läuft, können einzelne Felder noch leer sein — das ist erwartbar. Alternativ list_invoices aufrufen (neueste zuerst) und prüfen, dass der neue Beleg oben auftaucht.

  4. Ergebnis melden. invoice_id, aktueller status und ggf. Duplikat-Hinweis knapp zusammenfassen.

Hinweise

  • Pro Aufruf wird eine Datei hochgeladen. Bei mehreren Belegen den Upload je Datei wiederholen.
  • Niemals erfundene file_path-Werte verwenden — nur tatsächlich vorhandene, vom Nutzer genannte Dateien.
  • get_invoice/list_invoices liefern bewusst nur eine PII-freie Kurzfassung (kein OCR-Text, keine Steuer-IDs).

Prompt-Vorlage

Lade einen Beleg nach Fintaro hoch und verifiziere ihn.

Datei: <ABSOLUTER_PFAD_ZUR_DATEI>  (PDF/PNG/JPEG/WebP, ≤ 25 MB)

1. Stelle sicher, dass mein Key den Scope invoices:write hat (sonst abbrechen).
2. Rufe upload_invoice(file_path="<ABSOLUTER_PFAD_ZUR_DATEI>") auf und nenne mir
   invoice_id, status und ob es als Duplikat erkannt wurde (deduplicated).
3. Rufe get_invoice(invoice_id) für die zurückgegebene ID auf und zeig mir die
   Kurzfassung. Leere Felder sind ok, solange die Verarbeitung noch läuft.
4. Fasse das Ergebnis in 1-2 Sätzen zusammen.

Read the full file on GitHub · 63 lines

Changes

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.

  1. 11d ago First seen · 63 lines · 76 tokens per session scan A 0dd03ec753ae

Subscribe to this mod's changes

fintaro-belege-upload is a skill published in the GitHub repository fintaro-ai/fintaro-mcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 780 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-31.