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 NexFlow-SMF/nexflow-smf-public --skill smf-settlement-receiptgit clone --depth 1 https://github.com/NexFlow-SMF/nexflow-smf-publicWrote 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/nexflow-smf/nexflow-smf-public/smf-settlement-receipt)<a href="https://agentmods.dev/skills/nexflow-smf/nexflow-smf-public/smf-settlement-receipt"><img src="https://agentmods.dev/badge/skills/nexflow-smf/nexflow-smf-public/smf-settlement-receipt/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/nexflow-smf/nexflow-smf-public/smf-settlement-receipt"><img src="https://agentmods.dev/badge/skills/nexflow-smf/nexflow-smf-public/smf-settlement-receipt.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.00038 | $0.00444 |
| Opus 5 | $0.00019 | $0.00222 |
| Sonnet 5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
nexflow-smf-settlement-receipt-v1 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 11d 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.
What it actually says
When to use this skill
Use this skill when:
- A payment has already been settled via NexFlow/x402.
- You need a machine-readable record to store in logs, dashboards, or invoices.
- You are verifying that a prior payment actually completed before taking another step.
HTTP API
- Method: GET
- URL:
https://api.nexflow.xyz/api/smf/v1/settlement-receipt
Query parameters:
- payment_id (string, required): Unique identifier returned by NexFlow SMF at settlement time.
Example:
GET /api/smf/v1/settlement-receipt?payment_id=0x1234abcd...
Success response
{
"payment_id": "0x1234abcd...",
"status": "settled",
"network": "eip155:8453",
"asset": "USDC",
"amount": "10.00",
"fee": "0.03",
"facilitator": "base-main-smf",
"settled_at": "2026-02-17T16:20:00Z"
}
If status is not "settled", do not treat the funds as finalized.
Pricing
This endpoint is free.
It is safe to call repeatedly for monitoring and record-keeping.
Test usage
For test environments:
- Use known test
payment_idvalues provided by NexFlow (e.g. IDs starting withtest_). - Expect deterministic mock receipts suitable for automated tests.
Usage examples for agents
- "Verify that payment <payment_id> is settled before shipping goods."
- "Log the fee and facilitator for payment <payment_id> to the NexFlow audit log."
- "Generate a human-readable summary of payment <payment_id> for an invoice email."
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.
- 11d ago First seen · 65 lines · 38 tokens per session scan A 448d78135473
nexflow-smf-settlement-receipt-v1 is a skill published in the GitHub repository NexFlow-SMF/nexflow-smf-public (0 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 444 once invoked, about $0.0002 per session on Opus 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
piprail
Pay x402 paywalled URLs from a budget-bound, self-custodial crypto wallet across 10+ chains.
pinion-chain-intel
On-chain intelligence, transactions and wallet tools on Base. 9 x402-paywalled skills at $0.01 USDC each.
pinion-trade
Get an unsigned swap transaction via 1inch aggregator on Base. Includes approval tx if needed. Costs $0.01 USDC via x402.
pinion-fund
Check wallet balances and get funding instructions for Base. ETH and USDC. Costs $0.01 USDC via x402.
pinion-price
Get current USD price for any token on Base via Birdeye (CoinGecko fallback). Costs $0.01 USDC via x402.
pinion-send
Construct an unsigned ETH or USDC transfer transaction on Base. Client signs and broadcasts. Costs $0.01 USDC via x402.