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 skills add sumup/sumup-skills --skill upgrade-sumupgit clone --depth 1 https://github.com/sumup/sumup-skillsWrote 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/sumup/sumup-skills/upgrade-sumup)<a href="https://agentmods.dev/skills/sumup/sumup-skills/upgrade-sumup"><img src="https://agentmods.dev/badge/skills/sumup/sumup-skills/upgrade-sumup.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.1 | $0.00066 | $0.00661 |
| Opus 5 | $0.00033 | $0.00331 |
| Sonnet 5 | $0.00013 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
upgrade-sumup 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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SumUp Upgrade and Migration Guide
Knowledge and APIs can change. Always prefer current official docs and release notes.
- Docs root:
https://developer.sumup.com/ - LLM entrypoint:
https://developer.sumup.com/llms.txt
Use this skill when the request is about upgrades, version bumps, deprecations, or migrations.
Supported Upgrade Targets
- Node:
@sumup/sdk - Go:
sumup-go - Python:
sumup - PHP, Java, Rust, .NET SDK/client integrations
- iOS Terminal SDK
- Android Reader SDK
- Swift Checkout SDK
- React Native SDK
- Checkouts API and related webhook/3DS endpoint usage
Upgrade Workflow
1) Pre-upgrade inventory
Capture:
- Current SDK/library versions by service/app.
- All used SumUp endpoints and fields.
- Auth mode (API key/OAuth), scopes, and webhook signature setup.
- Environments impacted (sandbox, staging, production).
2) Breaking-change diff
For each SDK or endpoint migration:
- Compare changelog and migration notes.
- Identify renamed/removed fields, enums, and callback signatures.
- Identify behavior changes in async/payment status semantics.
- Identify deprecated endpoints and required replacements.
3) Migration implementation
- Upgrade one surface at a time (server SDK, then mobile SDK, then UI integration).
- Keep a compatibility adapter where necessary to isolate application code from SDK changes.
- Replace deprecated endpoints with current equivalents, preferring endpoints that accept
merchant_codewhere applicable. - Keep webhook verification and idempotency logic unchanged unless required.
4) Post-upgrade validation
- Run happy path payment in sandbox.
- Run deliberate failure (
amount = 11) and verify order state remains unpaid. - Verify 3DS redirect/challenge and return handling.
- Verify webhook retries and idempotent processing.
- Verify duplicate reference behavior and reconciliation fields.
5) Rollout and rollback
- Roll out in stages (internal -> low-volume -> full traffic).
- Add release toggles where practical.
- Keep previous version rollback path ready until metrics are stable.
What ships with it
3 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.
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.
- 7d ago First seen · 87 lines · 66 tokens per session scan A 436ba1caf1d7
upgrade-sumup is a skill published in the GitHub repository sumup/sumup-skills (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 661 once invoked, about $0.0003 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
x402-list
Discover x402 payment services and on-chain-verified facilitator settlement volume via the x402-list directory. Use when a user or agent needs to find an API/service that accepts x402 (HTTP 402 stablecoin) payments, compare services by reliability and price, check service uptime/health, see whether a service has…
recipe-create-expense-tracker
Set up a Google Sheets spreadsheet for tracking expenses with headers and initial entries.
starknet-mini-pay
Simple P2P payments on Starknet. Generate QR codes, payment links, invoices, and transfer ETH/STRK/USDC. Like Lightning, but native.
starknet-tongo
Confidential ERC20 payments on Starknet using Tongo protocol. Fund, transfer, withdraw, and rollover encrypted token balances with zero-knowledge proofs. Use when the user needs privacy-preserving transactions, confidential payments, encrypted balances, or auditable private transfers on Starknet.
finance-expert
Expert-level financial systems, FinTech, banking, payments, and financial technology. Use when the user mentions fintech, banking, payments, trading, or accounting, or when the task involves Financial Systems, FinTech Stack, Key Challenges, or Data Handling.
banking-expert
Expert-level banking systems, core banking, regulations, and banking technology. Use when the user mentions finance, core banking, regulations, or payments, or when the task involves Banking Systems or Key Technologies.