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 instructions/glowhub-1028/payment-flow/agents-mdgit 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/instructions/glowhub-1028/payment-flow/agents-md)<a href="https://agentmods.dev/instructions/glowhub-1028/payment-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/glowhub-1028/payment-flow/agents-md.svg" alt="Measured on agentmods" 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 | $0.03854 | $0.03854 |
| Opus 5 | $0.01927 | $0.01927 |
| Sonnet 5 | $0.00771 | $0.00771 |
| Haiku 4.5 | $0.00385 | $0.00385 |
Grade A, and why
payment-flow AGENTS.md 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 4d 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.
This is a copy
100% identical to inflow-cli AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Operating notes for working in this repo. If anything below conflicts with the configs (eslint.config.js,
typedoc.json, tsconfig.base.json, turbo.json, .changeset/config.json, .prettierrc.json), the configs win — fix
the drift, don't paper over it.
What this repo is
inflow is the agent-native and human-accessible command-line entry point to InFlow. It lets agentic buyers perform
agent-native payments via MPP and x402, and lets humans hit the same functionality from MCP-integrated assistants or the
raw CLI.
A pnpm + Turborepo monorepo with two packages:
@inflowpayai/inflow-core(packages/core) — the headless InFlow client. One augmented handle per command group hung off theInflowinstance:inflow.auth(IAuth),inflow.user(IUser),inflow.balances(IBalanceResource),inflow.depositAddresses(IDepositAddressResource),inflow.x402(IX402),inflow.mpp(IMpp). Each handle carries the typed HTTP primitives plus the command-shaped operations (reducers + async-iterable drivers for the stateful commands). No UI dependencies; an ESLintno-restricted-importsrule scoped topackages/core/src/**enforces this.@inflowpayai/inflow(packages/cli) — the published binary. Consumes the core package; renders Ink/React for TTY mode and structured output for agent mode. The CLI commands are thin render shells over the core flows.
Repo map
packages/cli/—@inflowpayai/inflow, the published binary.packages/core/—@inflowpayai/inflow-core, the typed HTTP client.plugins/inflow/— the plugin bundle:.claude-plugin/plugin.json,.cursor-plugin/plugin.json,.codex-plugin/plugin.json, plus symlinksskills → ../../skills,.mcp.json → ../../.mcp.json,assets → ../../assets(so each per-plugin manifest's./skills/,./.mcp.json, and./assets/paths resolve).skills/agentic-payments/SKILL.md— the single skill file..claude-plugin/marketplace.json— Claude Code marketplace entry..cursor-plugin/marketplace.json— Cursor marketplace entry..agents/plugins/marketplace.json— agents marketplace entry..codex-plugin/plugin.json— Codex marketplace entry..mcp.json— raw MCP entry.scripts/— repo-level dev/CI scripts..changeset/— pending version bumps.
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.
- 4d ago First seen · 218 lines · 3,854 tokens per session scan A d1464b152ee4
payment-flow AGENTS.md is an instructions file published in the GitHub repository glowhub-1028/payment-flow (0 stars, last pushed 2mo ago), licensed MIT. It adds 3,854 tokens to every session, about $0.0193 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to inflow-cli AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).