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 agentmods add skills/inflowpayai/inflow-cli/agentic-paymentsnpx skills add inflowpayai/inflow-cli --skill agentic-paymentsgit clone --depth 1 https://github.com/inflowpayai/inflow-cliWhat 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 | $0.00054 | $0.07237 |
| Opus 5 | $0.00027 | $0.03619 |
| Sonnet 5 | $0.00011 | $0.01447 |
| Haiku 4.5 | $0.00005 | $0.00724 |
Grade C, and why
agentic-payments scanned grade C with 2 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| macOS/Linux hosted installer | `curl -fsSL https://inflowcli.ai/install.sh \| bash` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: ['Bash(inflow:*)', 'Bash(brew:*)', 'Bash(curl:*)'] How it starts
The opening of the file, as written. The whole thing — 373 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 the signed native CLI through one of these channels:
| Channel | Command |
|---|---|
| macOS Homebrew | brew tap inflowpayai/tap && brew install --cask inflow |
| macOS/Linux hosted installer | curl -fsSL https://inflowcli.ai/install.sh | bash |
| Windows PowerShell installer | irm https://inflowcli.ai/install.ps1 | iex |
| Cross-platform shell compatibility | curl -fsSL https://inflowcli.ai/cli | bash |
Current install instructions live at https://inflowcli.ai/.
Running
InFlow runs as a standalone CLI or an MCP server.
MCP: add an inflow server to your MCP client config that runs inflow --mcp.
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>identifies a legacy plaintext credential file for deletion; it is not a credential backend.--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.
- 3d ago First seen · 373 lines · 54 tokens per session scan C c65395913377
agentic-payments is a skill published in the GitHub repository inflowpayai/inflow-cli (9 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 7,237 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
intelligent-oracle
Design, deploy, and monitor a GenLayer Intelligent Oracle prediction market from any coding agent. Use when a user wants to create a settled-by-web-evidence prediction market without opening the web UI.
jupiter-lend
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
lifi
LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits (Composer), yield discovery (Earn), and intent-based execution (Intents). USE THIS SKILL WHEN USER WANTS TO: Swap tokens between different blockchains (e.g., "swap USDC on Ethereum to ETH on Arbitrum") Bridge tokens to another chain…
x402-erc7710
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
lifi-stablecoin-swap
Build a production 1:1 stablecoin swap with LI.FI Intents — an interface or backend where the amount the user sends equals the amount they receive (no visible gas or solver fees), same-chain or cross-chain, filled by LI.FI's solver network and verifiable on-chain. USE THIS SKILL WHEN USER WANTS TO: Build a 1:1…
alkahest-user
Interact with Alkahest escrow contracts as a buyer, seller, or oracle using the CLI.