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.
/plugin marketplace add inflowpayai/inflow-clinpx agentmods add plugins/inflowpayai/inflow-cli/inflowgit clone --depth 1 https://github.com/inflowpayai/inflow-cliGrade A, and why
inflow 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- inflow — 88% identical, 2 lines differ
What it actually says
{
"name": "inflow",
"version": "0.12.1",
"description": "Authenticate with InFlow, inspect balances and deposit addresses, and perform agent-native payments via x402 and MPP.",
"author": {
"name": "Jarwin, Inc."
},
"keywords": ["onboarding", "payments", "x402", "mpp", "agentic", "inflow", "wallet"],
"skills": "./skills/",
"mcpServers": "./.mcp.json"
}
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.
- yesterday First seen · 12 lines scan A 927086850407
inflow is a plugin published in the GitHub repository inflowpayai/inflow-cli (9 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
internet-court-skill
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
internet-court-skill
Internet Court — the trust layer for agent-to-agent commerce.
optifeed-radar
Ask real AI engines real buyer questions and score whether a brand gets recommended. CLI plus an MCP server, running locally with your own API keys.
optifeed
AI visibility and commerce tools from Optifeed.
medusa-agent-skills
Plugin marketplace listing 4 plugins: medusa-dev, learn-medusa, ecommerce-storefront, medusa-cloud.
agentic-commerce
Plugin marketplace listing 15 plugins: ucp-agentic-commerce, acp-agentic-commerce, a2a-multi-agent, ap2-agentic-payments, magento2-commerce.