stripe/link-cli is a command-line tool that lets agents obtain temporary payment credentials from a Link wallet for approved purchases without exposing the user's real card details. It is used by agents to complete web checkouts or programmatic payments while requiring purchase approval. The catalogue entries provide components for integrating the CLI with agents.
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 stripe/link-cli --skill complete-link-purchasegit clone --depth 1 https://github.com/stripe/link-cliWrote 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/stripe/link-cli/complete-link-purchase)<a href="https://agentmods.dev/skills/stripe/link-cli/complete-link-purchase"><img src="https://agentmods.dev/badge/skills/stripe/link-cli/complete-link-purchase/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.
<a href="https://agentmods.dev/skills/stripe/link-cli/complete-link-purchase"><img src="https://agentmods.dev/badge/skills/stripe/link-cli/complete-link-purchase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01936 |
| Opus 5.5 | $0.00026 | $0.00774 |
| Sonnet 5.5 | $0.00013 | $0.00387 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
complete-link-purchase 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 2mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete a Link purchase
Link issues one-time-use payment credentials against a spend request — a single purchase the user has explicitly authorized for a stated amount and merchant.
You facilitate every spend approval through the request_virtual_card tool.
It shows the user a card with the amount, the merchant, your reason, and the
cart broken down line by line. Nothing is created unless they approve.
Everything after approval runs through the Link MCP server's tools. There is no CLI to install and no shell command to run.
Tools
| Tool | Use |
|---|---|
request_virtual_card |
Ask the user to authorize a purchase |
get_userinfo |
Confirm which Link account is connected |
get_spend_request |
Poll for approval, then retrieve the credential |
list_spend_requests |
See requests already in flight |
list_payment_methods |
See the wallet's cards and bank accounts |
list_shipping_addresses |
Fill a merchant's delivery fields |
sign_web_bot_auth |
Prove your identity to a merchant |
report_agent_observation |
Tell Link how the attempt went |
Flow
- Step 1: Confirm an account is connected
- Step 2: Price the purchase and read the merchant
- Step 3: Ask the user to authorize the card
- Step 4: Poll, then retrieve the credential
- Step 5: Pay
- Step 6: Report the outcome
Step 1: Confirm an account is connected
Call get_userinfo. If it fails with an authorization error, the user has not
connected Link in Cursor — say so and stop, rather than retrying.
Step 2: Price the purchase and read the merchant
Do this thoroughly before raising a card. The amount you ask for is the exact amount that gets charged, and a card issued for less than the cart total is declined at checkout. Changing your mind means asking the user all over again.
- Open the merchant page and read how it accepts payment. A normal credit-card checkout form is the ordinary case, and the issued card works there.
- Get the final total: items, tax, shipping, and any fees.
- Know exactly what is being bought — size, colour, delivery option — so the line items you show the user match their cart.
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.
- 2mo ago First seen · 178 lines · 64 tokens per session scan A 03ce5496ec24
complete-link-purchase is a skill published in the GitHub repository stripe/link-cli (882 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,936 once invoked, about $0.0003 per session on Opus 5.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
asc-ppp-pricing
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.
snaplii-cli
Snaplii for Claude: buy discounted gift cards across 500+ brands with vouchers and up to 10% cashback, check the Snaplii Cash balance, pay bills (Canada) and send money to a phone number, through the snaplii MCP tools or the snaplii CLI, spending only the user's prepaid Snaplii Cash within the spending limit they set.…
stripe
Stripe API integration with managed OAuth. Manage customers, subscriptions, invoices, products, prices, and payments. Use this skill when users want to process payments, manage billing, or handle subscriptions with Stripe. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).…
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…
shopify-admin-chargeback-watchlist-tagger
Identifies customers with disputed or charged-back orders and tags their customer record for proactive review on future orders.
shopify-admin-payout-reconciliation
Read-only: reconciles Shopify Payments payouts against the order transactions that funded them and flags amount discrepancies.