agents-pay

agents-pay is a skill for Claude Code, Codex from aws/agent-toolkit-for-aws. It costs 183 tokens per session (5,991 once invoked), scanned A, original, Apache-2.0.

A workflow for letting an AI agent pay for x402-protected online content. An x402 payment is a payment requested by a web service when a request receives HTTP status 402.

In plain words
What is it for?
Use it when an agent encounters a paywall, needs bounded per-payment or session budgets, or must settle an approved payment at runtime.
Why use it?
It keeps payment decisions and spending limits in code, so fetched content or model instructions cannot change who gets paid or how much.

Skill for Claude CodeCodex

Part of the aws-agents plugin — 8 skills shipped together

About the project

Agent Toolkit for AWS is a collection of AWS-supported MCP servers, skills, plugins, commands, and hooks that help AI coding agents build, deploy, and manage applications on AWS. It is used by developers working with AWS services through agents such as Claude Code, Codex, Cursor, and Kiro. The catalogue entries are the toolkit's own agent extensions for AWS development and operations.

aws/agent-toolkit-for-aws · 2,533 stars · on GitHub

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.

agentmods
npx agentmods add skills/aws/agent-toolkit-for-aws/agents-pay
Any agent
npx skills add aws/agent-toolkit-for-aws --skill agents-pay
Clone the repo
git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws

Made for: Claude Code, Codex.

Or install aws-agents, the plugin that ships this one along with the rest of its 8 skills.

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 agents-pay

README.md
[![agentmods](https://agentmods.dev/badge/skills/aws/agent-toolkit-for-aws/agents-pay.svg)](https://agentmods.dev/skills/aws/agent-toolkit-for-aws/agents-pay)
Your own site
<a href="https://agentmods.dev/skills/aws/agent-toolkit-for-aws/agents-pay"><img src="https://agentmods.dev/badge/skills/aws/agent-toolkit-for-aws/agents-pay.svg" alt="Measured on agentmods" height="20"></a>
Per session 183 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,991 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00183 $0.05991
Opus 5 $0.00092 $0.02995
Sonnet 5 $0.00037 $0.01198
Haiku 4.5 $0.00018 $0.00599

Measured 5d ago against content hash f58b2685ccf5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agents-pay 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 5d ago.

The scan reads SKILL.md. This mod also ships 17 executable files (packages/openclaw/runtime/agentcore_bridge.py, packages/openclaw/scripts/stage-skill.mjs, packages/openclaw/src/bridge.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/aws-agents/skills/agents-pay/SKILL.md · 549 lines

How it starts

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

pay

Let an agent pay for x402-protected content without letting the agent — or anything it reads — decide who gets paid, how much, or how often.

The one idea that matters

A payment decision is made in code, from a policy file, before any signing. Nothing the model says, and nothing inside fetched content, can authorize a payment or raise a limit.

An instruction to a model is not an access control: it is a request that a confused or prompt-injected model may decline. Controls must be enforced in code at the point where payment is authorised.

So in this skill every control is executable, and the model's entire payment surface can only spend an already-approved, bounded session — it can pay, check remaining budget, and obtain an opaque handle for a browser navigation, and nothing more.

When to use

This skill is for an agent that needs to pay for something itself, right now — the coding agent you are talking to, or an agent host like OpenClaw, hitting a paywall mid-task and settling it.

  • The agent you are running hits an x402 paywall (HTTP 402) and needs the content
  • You need hard spend limits on what that agent can pay, per payment and per session
  • A payment was refused and you need to know which rule rejected it

Not this skill: building a payment-capable agent

If you are writing an agent that will take payments or pay on behalf of its own end users — provisioning a wallet per customer, wiring a payments plugin or middleware into a product you are shipping — that is the agents-build skill and its references/payments.md. It covers the framework-native integrations and the per-end-user data plane.

The distinction is who spends:

agents-buildreferences/payments.md agents-pay (this skill)
Question "How do I give the agent I'm building the ability to pay?" "This agent needs to pay for this thing now"
When Build time, in a product you ship Run time, in the session you are in
Wallet One per end user of your product One for this installation
Who approves spend Your product's own flow The operator, at a terminal

Read the full file on GitHub · 549 lines

Files

What ships with it

33 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 5d ago First seen · 549 lines · 183 tokens per session scan A f58b2685ccf5

Subscribe to this mod's changes

agents-pay is a skill published in the GitHub repository aws/agent-toolkit-for-aws (2,533 stars, last pushed today), licensed Apache-2.0. It adds 183 tokens to every session and 5,991 once invoked, about $0.0009 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-30.