agentmods.dev

yolfi-payments

yolfi-payments is a skill for Claude Code from yolfinance/yolfi-agent. It costs 37 tokens per session (1,028 once invoked), scanned A, a copy of yolfi-payments, MIT.

A workflow for adding Yolfi crypto payments to an application, including checkout, payment links, subscriptions, donations, and webhook-based access rules.

In plain words
What is it for?
Use it to inspect an app's existing checkout and server routes, configure Yolfi access, add payment flows, and handle payment webhooks.
Why use it?
It guides the setup of authentication, payment handling, and webhook processing so an app can connect payments to user access or other outcomes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the yolfi-agent plugin — 2 skills, 2 MCP servers shipped together

not rated 188repo 1mo ago A scan 37 tokens copy · 100% MIT

Good fit Use it to inspect an app's existing checkout and server routes, configure Yolfi access, add payment flows, and handle payment webhooks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yolfinance/yolfi-agent/yolfi-payments
View source ↗ yolfinance/yolfi-agent yolfi.com
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 yolfinance/yolfi-agent --skill yolfi-payments
Clone the repo
git clone --depth 1 https://github.com/yolfinance/yolfi-agent

Made for: Claude Code.

Or install yolfi-agent, the plugin that ships this one along with the rest of its 2 skills, 2 MCP servers.

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 yolfi-payments

README.md
[![agentmods](https://agentmods.dev/badge/skills/yolfinance/yolfi-agent/yolfi-payments/github.svg)](https://agentmods.dev/skills/yolfinance/yolfi-agent/yolfi-payments)
Your own site
<a href="https://agentmods.dev/skills/yolfinance/yolfi-agent/yolfi-payments"><img src="https://agentmods.dev/badge/skills/yolfinance/yolfi-agent/yolfi-payments/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 yolfi-payments

Your own site · 80×15
<a href="https://agentmods.dev/skills/yolfinance/yolfi-agent/yolfi-payments"><img src="https://agentmods.dev/badge/skills/yolfinance/yolfi-agent/yolfi-payments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,028 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 100% copy Near-identical to another mod 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.00037 $0.01028
Opus 5 $0.00018 $0.00514
Sonnet 5 $0.00007 $0.00206
Haiku 4.5 $0.00004 $0.00103

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

Security

Grade A, and why

yolfi-payments 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.

Origin

This is a copy

100% identical to yolfi-payments — 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.

skills/yolfi-payments/SKILL.md · 50 lines

How it starts

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

Yolfi Payments Skill

Use this when the user asks to add crypto payments, payment links, checkout, subscriptions, donations, or webhook-based entitlements with Yolfi.

Workflow

  1. Inspect the target app first.
  2. Identify the framework, env system, server routes, existing checkout code, existing webhook handlers, and entitlement logic.
  3. Check auth with yolfi auth:status or yolfi_auth_status; an explicit YOLFI_API_KEY takes precedence over the protected local credential.
  4. If auth is missing and the user already has a Yolfi account, use yolfi setup --agent <slug> followed by browser authorization and yolfi checkin --agent <slug>. The bundled plugin and local MCP server expose yolfi_agent_setup_start and yolfi_agent_checkin; manually configured remote MCP uses OAuth managed by the host instead. For a new user on the bundled/local transport, first ask them to confirm their email and project name, then call yolfi_agent_register. Ask them to open the emailed confirmation link, then call the same tool again with the same arguments. Existing emails must not be re-registered. The tool stores the credential locally, redacts it from model output, and reuses its pending idempotency key across confirmation check-ins.
  5. Ask the user for settlement wallet addresses. Never invent them.
  6. Ask the user for product name, price, currency, payment type, and recurring interval.
  7. Configure settlement settings through PUT /api/private/organization/current, then create each webhook through POST /api/private/organization/webhook-endpoints. The CLI/local MCP stores the one-time signing secret in the protected local Yolfi config and redacts it from output.
  8. List existing paylinks before creating a new one.
  9. Create or reuse a paylink.
  10. Store paylink ids in env/config, not hard-coded source when avoidable.
  11. Add checkout UI or a server route that calls POST /api/public/payments. Pass a stable merchant-side customer/user id as clientReferenceId whenever webhook-driven attribution or subscription lifecycle updates must resolve that customer.
  12. Add webhook signature verification for X-Yolfi-Signature. In native (NONE) payloads read data.customer.clientReferenceId; Stripe-compatible Checkout Session uses data.object.client_reference_id, while Stripe-compatible Invoice and Subscription objects use data.object.metadata.client_reference_id; Lemon Squeezy-compatible payloads use meta.custom_data.client_reference_id.
  13. Connect webhook events to the app's existing entitlement/business logic when possible.
  14. Verify payment status with GET /api/public/payments/:id.
  15. Report changed files and exact verification commands.

Read the full file on GitHub · 50 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 · 50 lines · 37 tokens per session scan A e42cf3987596

Subscribe to this mod's changes

yolfi-payments is a skill published in the GitHub repository yolfinance/yolfi-agent (188 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,028 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 yolfi-payments, differing in 0 lines, and is treated as a copy.

Finance and fintechWeb3 and blockchainai-agentscheckoutcrypto-paymentsmcppaymentsstablecoin-payments
Related

Other skills, from other repositories

piprail

Pay x402 paywalled URLs from a budget-bound, self-custodial crypto wallet across 10+ chains.

piprail/piprail · 28 tokens

starknet-mini-pay

Simple P2P payments on Starknet. Generate QR codes, payment links, invoices, and transfer ETH/STRK/USDC. Like Lightning, but native.

keep-starknet-strange/starknet-agentic · 40 tokens

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.

keep-starknet-strange/starknet-agentic · 61 tokens

fintech-expert

Expert in financial technology, payment processing, open banking APIs, PSD2, blockchain in finance, robo-advisors, and RegTech. Use when the user mentions payments, open banking, PSD2, blockchain, cryptocurrency, or robo advisor, or when the task involves Payment Processing, Blockchain in Finance, Payment Security, or…

personamanagmentlayer/pcl · 73 tokens

splits

Use Splits with Bankr for onchain treasury operations: secure assets, process revenue, manage operating subaccounts, pay expenses, govern contracts, and maintain clean accounting books.

BankrBot/skills · 38 tokens

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…

mcccsm/x402-list-mcp · 99 tokens