payment-session

payment-session is a skill for Claude Code, Codex from Parad0x-Labs/openclaw-skills. It costs 50 tokens per session (714 once invoked), scanned A, original, MIT.

A billing session tracker for OpenClaw agents using x402, a system for paying for individual online calls. It supports pay-as-you-go usage or recurring subscription charges without holding money or private keys.

In plain words
What is it for?
Use it to open capped billing sessions, record usage, check when payment is due, record completed payments, and settle any final remainder.
Why use it?
It groups small charges into settlements and limits the total amount a session can spend, reducing transaction overhead and runaway billing risk.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to open capped billing sessions, record usage, check when payment is due, record completed payments, and settle any final remainder.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/parad0x-labs/openclaw-skills/payment-session
Install

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.

Any agent
npx skills add Parad0x-Labs/openclaw-skills --skill payment-session
Clone the repo
git clone --depth 1 https://github.com/Parad0x-Labs/openclaw-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for payment-session

README.md
[![agentmods](https://agentmods.dev/badge/skills/parad0x-labs/openclaw-skills/payment-session/github.svg)](https://agentmods.dev/skills/parad0x-labs/openclaw-skills/payment-session)
Your own site
<a href="https://agentmods.dev/skills/parad0x-labs/openclaw-skills/payment-session"><img src="https://agentmods.dev/badge/skills/parad0x-labs/openclaw-skills/payment-session/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.

agentmods 80×15 button for payment-session

Your own site · 80×15
<a href="https://agentmods.dev/skills/parad0x-labs/openclaw-skills/payment-session"><img src="https://agentmods.dev/badge/skills/parad0x-labs/openclaw-skills/payment-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 714 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00714
Opus 5.5 $0.00020 $0.00286
Sonnet 5.5 $0.00010 $0.00143
Haiku 4.5 $0.00005 $0.00071

Measured 23d ago against content hash 9eac3e13ec8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

payment-session 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 23d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (src/index.ts, src/session.ts, src/tools.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/payment-session/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Payment Session

x402 is discrete per-call. This adds the two billing shapes it lacks, settled in batches through x402 so you pay one transaction per settlement (not per tick — the only economical way to bill micro-usage given fees + ATA rent):

  • metered (pay-as-you-go): accrue per-use charges, settle when they cross a threshold.
  • subscription (streaming): charge a fixed amount every period.

Pure accounting — it never moves money or holds a key. It tells the agent when and how much to settle; the agent pays via x402-pay's pay_x402. A maxTotalUsdc lifetime budget bounds what the session suggests and records; it does not stop pay_x402 from paying a larger seller quote (see Trust model).

Tools

Tool Does
open_payment_session start a metered or subscription session with a maxTotalUsdc cap
meter_usage accrue pay-as-you-go usage (metered sessions)
check_settlement_due is a payment due, and for how much? (amount is capped at remaining budget)
record_settled record a paid settlement after pay_x402 succeeds
close_payment_session close; returns any final remainder to settle

The loop

open_payment_session(payee, mode, cap)
  metered:      meter_usage(...)  → check_settlement_due → if due: pay_x402(payee, amount) → record_settled
  subscription: (time passes)     → check_settlement_due → if due: pay_x402(payee, amount) → record_settled
close_payment_session  → settle any remainder

Trust model

  • Non-custodial. This plugin only does accounting; the actual USDC settlement is pay_x402 (your own wallet signs). It never holds a key or moves funds.
  • Budget-capped accounting, not spend enforcement. Every session has a maxTotalUsdc budget: check_settlement_due never suggests more than the remaining budget, and record_settled refuses to record more. The session does not control pay_x402, which pays the seller's quoted amount: a payment can exceed the suggested amount and the session budget. Per-payment spend is bounded by x402-pay's maxAmountUsdc (the 5 bps protocol fee is added on top of that cap). State is in memory and is lost on restart.

Read the full file on GitHub · 58 lines

Changes

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.

  1. 23d ago Changed · +4 lines · +1 tokens per session 9eac3e13ec8b
  2. 2mo ago First seen · 54 lines · 49 tokens per session scan A 29e910e7ceca

Subscribe to this mod's changes

payment-session is a skill published in the GitHub repository Parad0x-Labs/openclaw-skills (23 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 714 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-30.