New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Yolfi Payments

by yolfinance in yolfinance/yolfi-agent

Add Yolfi crypto checkout, payment links, and webhook handling to an app through @yolfi/agent or the Yolfi MCP server.

MITAuto-check passedBackend & APIs

Install Yolfi Payments

skills CLI
$ npx skills add yolfinance/yolfi-agent --skill yolfi-payments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yolfinance/yolfi-agent yolfi-payments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
yolfi-payments
GitHub stars
178
Token cost
~1.2k tokens
SKILL.md length
607 words
Files
56 (incl. assets)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Add Yolfi crypto checkout, payment links, and webhook handling to an app through @yolfi/agent or the Yolfi MCP server.

  • Works in 12 steps: Inspect the target app first. → Identify the framework, env system,… → Check auth with yolfi auth:status or… → …
  • Tasks that involve Webhooks
  • SKILL.md covers Workflow, Webhook Contract and Do Not
  • Needs YOLFI_API_KEY and YOLFI_WEBHOOK_SECRET

What it does

Yolfi Payments is an agent skill from yolfinance/yolfi-agent. Add Yolfi crypto checkout, payment links, and webhook handling to an app through @yolfi/agent or the Yolfi MCP server.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 62 other files, including assets (for example `.claude-plugin/plugin.json`, `.codex-plugin/plugin.json` and `.github/workflows/package-check.yml`).

It sits in Backend & APIs, covering Webhooks, MCP servers and Crypto and DeFi analysis. It works with Model Context Protocol. The repository describes itself as: Yolfi Agent Kit SDK, CLI, and MCP server for AI coding agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Webhooks
  • Tasks that involve MCP servers
  • Tasks that involve Crypto and DeFi analysis

Example prompts

  • “/yolfi-payments”

Requirements

  • A credential in YOLFI_API_KEY
  • A credential in YOLFI_WEBHOOK_SECRET

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  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 followed by browser authorization and yolfi checkin…
  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…
  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…
  12. Add webhook signature verification for X-Yolfi-Signature. In native (NONE) payloads read data.customer.clientReferenceId…

What it can do on your machine

Read from SKILL.md and the folder at commit 9a43754. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • YOLFI_API_KEY
    • YOLFI_WEBHOOK_SECRET

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Yolfi Payments loads about 1.2k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 607 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yolfinance/yolfi-agent at commit 9a43754, republished under its MIT licence (© yolfinance). 607 words, ~1,190 tokens.

Download SKILL.mdSave it as .claude/skills/yolfi-payments/SKILL.md (or your agent's skills folder). This skill also uses 55 other files; get the full folder from GitHub.
name
yolfi-payments
description
Add Yolfi crypto checkout, payment links, and webhook handling to an app through @yolfi/agent or the Yolfi MCP server.

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.
Show full SKILL.md (255 more words)Show less

Webhook Contract

  • Publicly supported endpoint adapters are NONE, STRIPE, and LEMON_SQUEEZY. Treat NONE as native Yolfi payload format, not as the absence of a provider.
  • Create independent endpoints through POST /api/private/organization/webhook-endpoints; the removed organization-level webhookUrl and webhookAdapter fields are not supported.
  • Each endpoint has its own signing secret. CLI/MCP create and rotate store it in the protected local config; use the endpoint id for local verification or provision YOLFI_WEBHOOK_SECRET through the target deployment's secret manager.
  • YOLFI_API_KEY authorizes Yolfi API calls and must never be used to verify webhook signatures. Verify X-Yolfi-Signature with that endpoint's signing secret only.
  • Endpoint create/update accepts optional flat metadataFilters string maps (at most 10 entries; keys at most 100 characters; values at most 255 characters); a delivery must match every configured key/value.
  • Browser setup and agent-first signup each issue a scoped yolfi_agent_* credential. Neither credential is a webhook signing secret.
  • Analytics routing uses website_id. Provision an adapter NONE endpoint with metadataFilters: { "website_id": "<websiteId>" }.

Do Not

  • Do not invent wallet addresses.
  • Do not invent prices, plans, currencies, or recurring intervals.
  • Do not commit API keys or webhook secrets.
  • Do not print or echo the yolfi_agent_* credential returned during check-in.
  • Do not pass webhook signing secrets as MCP arguments or CLI flags.
  • Do not replace existing billing logic unnecessarily.
  • Do not use frontend redirect as proof of payment.
  • Do not disable paylinks without explicit user approval.
  • Do not duplicate webhook business handlers when an existing handler can be reused.
  • Do not use email as the primary subscription identity when clientReferenceId can be supplied.

© yolfinance, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 55 other files (assets) in the repository root of yolfinance/yolfi-agent.

  • SKILL.md
  • .claude-plugin/plugin.json
  • .codex-plugin/plugin.json
  • .dockerignore
  • .github/workflows/package-check.yml
  • .gitignore
  • .mcp.json
  • Dockerfile
  • LICENSE
  • README.md
  • assets/ai-agent-payment.jpg
  • docs/agent-setup.md
  • docs/i18n/README.de.md
  • docs/i18n/README.es.md
  • … and 42 more

Open the folder on GitHubat commit 9a43754

Compare with similar skills

Yolfi Payments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Yolfi Payments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Yolfi Payments this skillyolfinance/yolfi-agent178—~1.2kAutomated safety check: PassMIT
X Twitter ScraperXquik-dev/x-twitter-scraper2111 repos~2.6kAutomated safety check: PassMIT
Zalo AgentPhucMPham/zalo-agent-cli166—~2.3kAutomated safety check: PassMIT
Frontmcp Channelsagentfront/frontmcp146—~3.7kAutomated safety check: PassApache-2.0
Arandu Integrationsarandu-io/arandu281—~3.1kAutomated safety check: PassMIT
E2a Doctortokencanopy/e2a193—~994Automated safety check: PassApache-2.0

Similar skills

  • X Twitter Scraper

    Xquik-dev/x-twitter-scraper

    Use Xquik to fetch X (Twitter) data or act through a connected account: search, profiles, followers, replies, threads, timelines, media downloads, bulk exports, trends, monitors, signed webhooks…

    211 GitHub starsUsed in 1 repo~2.6k tokens
    Backend & APIsAuto-check passed

  • Zalo Agent

    PhucMPham/zalo-agent-cli

    Automate Zalo messaging, Official Account (OA), and MCP server integration via zalo-agent-cli.

    166 GitHub stars~2.3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Frontmcp Channels

    agentfront/frontmcp

    A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.

    146 GitHub stars~3.7k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Arandu Integrations

    arandu-io/arandu

    Reaching other systems from an Arandu (Go) application, and letting them reach it -- the client of an external API with its interface and fake, webhooks sent and received, and tools, resources and…

    281 GitHub stars~3.1k tokensUpdated today
    Backend & APIsAuto-check passed

  • E2a Doctor

    tokencanopy/e2a

    A skill your agent uses when an existing e2a MCP connection, inbox, custom domain, protection policy, webhook, or message delivery is failing or unclear.

    193 GitHub stars~994 tokensUpdated 4 days ago
    Backend & APIsAuto-check passed

  • Helius for Solana

    internet-court/internet-court-skill

    Guides building Solana apps on Helius: sending transactions, asset and NFT queries, live streaming, webhooks, priority fees, wallet analysis and API key onboarding.

    6.6k GitHub starsUsed in 1 repo~2.7k tokens
    Backend & APIsAuto-check passed

Works with

Categories

Questions about Yolfi Payments

What does Yolfi Payments do?

Add Yolfi crypto checkout, payment links, and webhook handling to an app through @yolfi/agent or the Yolfi MCP server. Yolfi Payments is an agent skill from yolfinance/yolfi-agent. Add Yolfi crypto checkout, payment links, and webhook handling to an app through @yolfi/agent or the Yolfi MCP server.

When should I use Yolfi Payments?

Yolfi Payments fits situations like: tasks that involve Webhooks; tasks that involve MCP servers; tasks that involve Crypto and DeFi analysis.

How do I install Yolfi Payments in Claude Code?

Run `npx skills add yolfinance/yolfi-agent --skill yolfi-payments -a claude-code`. Or copy the skill folder (the yolfinance/yolfi-agent repository) into .claude/skills/yolfi-payments in your project. Claude Code loads it when a task matches its description.

How do I install Yolfi Payments in Codex?

Run `npx skills add yolfinance/yolfi-agent --skill yolfi-payments -a codex`. Or copy the skill folder (the yolfinance/yolfi-agent repository) into .agents/skills/yolfi-payments in your project. Codex loads it when a task matches its description.

Can I use Yolfi Payments in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yolfinance/yolfi-agent --skill yolfi-payments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/yolfi-payments, .gemini/skills/yolfi-payments, .github/skills/yolfi-payments and .opencode/skills/yolfi-payments in your project.

What does Yolfi Payments need to run?

Going by SKILL.md and its folder, Yolfi Payments needs credentials named YOLFI_API_KEY and YOLFI_WEBHOOK_SECRET. Our summary lists: A credential in YOLFI_API_KEY; A credential in YOLFI_WEBHOOK_SECRET.

Does Yolfi Payments access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Yolfi Payments safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Yolfi Payments use?

Yolfi Payments is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Yolfi Payments use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Yolfi Payments?

Skills that share tags, products or a category with Yolfi Payments: X Twitter Scraper (Xquik-dev/x-twitter-scraper, 211 stars), Zalo Agent (PhucMPham/zalo-agent-cli, 166 stars), Frontmcp Channels (agentfront/frontmcp, 146 stars) and Arandu Integrations (arandu-io/arandu, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Yolfi Payments?

yolfinance (a GitHub organization) maintains it in yolfinance/yolfi-agent, which has 178 GitHub stars. The repository was last updated on July 20, 2026.

Source: yolfinance/yolfi-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.