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 create-payment-credentialgit 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/create-payment-credential)<a href="https://agentmods.dev/skills/stripe/link-cli/create-payment-credential"><img src="https://agentmods.dev/badge/skills/stripe/link-cli/create-payment-credential/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/create-payment-credential"><img src="https://agentmods.dev/badge/skills/stripe/link-cli/create-payment-credential.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 73 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Memory Poisoning · line 124 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium MCP Rug Pull · line 8 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 9 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 61 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Excessive Agency · line 122 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00042 | $0.02421 |
| Opus 5.5 | $0.00017 | $0.00968 |
| Sonnet 5.5 | $0.00008 | $0.00484 |
| Haiku 4.5 | $0.00004 | $0.00242 |
Grade A, and why
create-payment-credential 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 today.
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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Payment Credential
Use Link to get payment credentials for the user's one-time or recurring purchase.
Call this extension's native tools with their discovered mount prefix, such as
link__create_spend_request. Tool schemas are the reference for input names and
constraints. Pass structured arguments, not command strings.
The tools support card credentials, Shared Payment Tokens (SPTs), and merchant-bound Link Pay Token (LPT) requests.
Core flow
- Confirm the wallet and any verification requirements.
- Confirm the spend-request inputs.
- Confirm the payment method and shipping details if needed.
- Create the spend request and obtain approval.
- Retrieve the approved credential.
1. Confirm the wallet
Link tools use the wallet configured by the application. If a tool prompts for Eve authorization, let the user finish it so the call can resume. Do not ask for tokens in chat. If authorization fails or is denied, explain the result and stop.
Call retrieve_user_info with {} when you need to confirm the connected user,
spend limits, balance eligibility, or verification requirements. If
agent_wallet_verification_requirement.action_url is present, show the user the
required action. Finite spend-limit values are cents; a returned null limit
means unlimited. Missing fields do not establish unlimited access or completed
verification.
2. Confirm the spend-request inputs
Use confirmed purchase details from the user or existing task context: the final
total including taxes and shipping, items, quantities, and delivery choices.
Ask for missing details before creating a request. Describe the actual purchase
in context; the user reads it when approving. It must be at least 100 characters.
Use the credential type established by those purchase details:
| Credential needed | create_spend_request inputs |
|---|---|
| Card form | credential_type: "card", with merchant_name and merchant_url |
| Supported Stripe programmatic payment flow | credential_type: "shared_payment_token", with the merchant's network_id |
| Link Pay Token | credential_type: "link_pay_token" and the checkout-provided merchant_account_id |
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.
- today Changed · +3 lines 35594fece6e6
- 2d ago Changed · +29 lines · +6 tokens per session a8d99062f18b
- 15d ago Changed · +9 lines 81edf65a0b64
- 16d ago Changed e042c32d29e7
- 23d ago Changed · -409 lines · -59 tokens per session 91d41305f28f
- 26d ago Changed · +11 lines 85cc9d0f8382
- 28d ago Changed · -42 lines 0d5efec557da
- 1mo ago Changed · +104 lines 91340553fb3b
- 1mo ago Changed · +42 lines 3e3a34670687
- 1mo ago First seen · 469 lines · 95 tokens per session scan A 114b75fed880
create-payment-credential is a skill published in the GitHub repository stripe/link-cli (865 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,421 once invoked, about $0.0002 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.