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 glowhub-1028/payment-flow --skill agentic-paymentsgit clone --depth 1 https://github.com/glowhub-1028/payment-flowWrote 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/glowhub-1028/payment-flow/agentic-payments)<a href="https://agentmods.dev/skills/glowhub-1028/payment-flow/agentic-payments"><img src="https://agentmods.dev/badge/skills/glowhub-1028/payment-flow/agentic-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.
<a href="https://agentmods.dev/skills/glowhub-1028/payment-flow/agentic-payments"><img src="https://agentmods.dev/badge/skills/glowhub-1028/payment-flow/agentic-payments.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.06451 |
| Opus 5.5 | $0.00022 | $0.02580 |
| Sonnet 5.5 | $0.00011 | $0.01290 |
| Haiku 4.5 | $0.00005 | $0.00645 |
Grade A, and why
agentic-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 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Payments
Pay HTTP 402-protected resources on the user's behalf. InFlow speaks two payment protocols - MPP and x402 - but the flow is the same for both: shared setup (install, run, authenticate), then a router that picks the protocol from the seller's 402 header, then one Paying a 402 resource section that covers both. A per-protocol delta table at the top of that section lists the handful of real differences (header name, credential name, filters, error codes); read your row, then follow the shared steps.
Installing
Install with npm install -g @inflowpayai/inflow. Or run directly with npx -y @inflowpayai/inflow.
Running
InFlow runs as a standalone CLI or an MCP server.
MCP: add an inflow server to your MCP client config that runs npx -y @inflowpayai/inflow --mcp. Keep the -y flag - it suppresses npx's confirmation prompt, without which the MCP host can stall on first run.
MCP mode exposes every CLI command as a tool. Call tools/list on the MCP server for the authoritative inventory; arguments mirror the CLI flags one-to-one.
Common commands / options
The CLI is the source of truth for exact flags, enums, and output shapes - run inflow <command> --schema for one command, or inflow --llms-full for everything. This playbook covers when and why, not exhaustive parameter lists; when you need a precise flag name, value set, or response shape, query the CLI rather than guessing.
inflow --llms(or--llms-fullfor parameter detail) - discover all commands.inflow <command> --schemafor a single command's JSON Schema.inflow --skill- print this playbook (no frontmatter) to stdout. Use it to paste into the system-prompt field of an MCP host that doesn't natively load skills:inflow --skill | pbcopy.- Default output is
toon. Override with--format <fmt>; for programmatic parsing preferjson(single document) orjsonl(line-delimited). - Multi-step flows return
_next.command- run it to continue. --auth <path>overrides the credentials file location.--api-key <key>orINFLOW_API_KEY=<key>is an alternative to device-flow auth.
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 · 323 lines · 54 tokens per session scan A 1f4297dc91a8
agentic-payments is a skill published in the GitHub repository glowhub-1028/payment-flow (0 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 6,451 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-31.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
tushare
A Python interface for Tushare, a financial data service that provides market and company information for stocks, funds, futures, and digital assets. It returns queried data as pandas tables.
stripe-best-practices
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax…
hyperliquid-websocket
Subscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-only. Use for…
crypto-market-data-service-guide
Guide to the Crypto Market Data TypeScript service — clean market data APIs for token prices, candles, market cap, and volume across multiple chains. Features caching, rate limiting, fallback sources, and WebSocket subscriptions. Built for production DeFi applications.
wechatpay-payment-integration
A Chinese-language guide for WeChat Pay, Tencent's payment service, covering product selection, integration, troubleshooting, and payment operations.