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 skills/mission69b/t2000/t2000-paynpx skills add mission69b/t2000 --skill t2000-paygit clone --depth 1 https://github.com/mission69b/t2000Wrote 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/mission69b/t2000/t2000-pay)<a href="https://agentmods.dev/skills/mission69b/t2000/t2000-pay"><img src="https://agentmods.dev/badge/skills/mission69b/t2000/t2000-pay.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.1 | $0.00075 | $0.00992 |
| Opus 5 | $0.00037 | $0.00496 |
| Sonnet 5 | $0.00015 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
t2000-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
t2000: Pay for x402 API Service
Status
Active — bundled with @t2000/cli (no separate install).
USDC payment is gasless. The 402 challenge response is a 0x2::balance::send_funds Move call, which is in Sui's foundation-sponsored allowlist. The wallet can pay even with 0 SUI in the gas reserve.
Purpose
Make a paid HTTP request to any x402-protected endpoint. Handles the 402 challenge, pays via Sui USDC, and returns the API response.
What this pays
Any endpoint that answers 402 with a Sui x402 challenge:
- an seller Service listed on the t2000 store (find one with
t2 services/t2000_services) — the seller runs the endpoint on their own origin and the payment settles straight to their wallet; or - any URL the user gives you, listed or not.
There is no t2000-hosted catalog of third-party provider URLs. t2000 resells
nothing, so never guess a provider URL — if the user hasn't given you one
and nothing is listed, say so and offer to post the work as an Open job
(t2 job open) for a seller to claim.
t2 services "image" # what's actually listed
t2 pay <url> --estimate # price a specific endpoint without paying
Command
t2 pay <url> [options]
Options
| Option | Description | Default |
|---|---|---|
--method <method> |
HTTP method (GET, POST, PUT) | GET (auto-promotes to POST when --data is set) |
--data <json> |
Request body for POST/PUT (JSON bodies default content-type: application/json) |
— |
--max-price <amount> |
Max USDC to auto-approve (enforced before any payment) | $1.00 |
--header <key=value> |
Additional HTTP header (repeatable) | — |
--estimate |
Show the price without paying (no funds spent) | — |
--force |
Override spending limits for this call (see t2 limit) |
— |
Price discovery
The seller's own 402 challenge is the source of truth for price. Never assume
one: t2 pay <url> --estimate returns what would be charged without paying,
and --max-price refuses anything above your ceiling before funds move.
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.
- 6d ago First seen · 101 lines · 75 tokens per session scan A 59102bfa5fd3
t2000-pay is a skill published in the GitHub repository mission69b/t2000 (23 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 992 once invoked, about $0.0004 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.
Other skills, from other repositories
swarmwage-publish
Publish your agent's capabilities to the Swarmwage registry and earn USDC for each call. Lets your agent advertise services (image generation, audio transcription, charting, custom domain workflows…) on the open agent hire protocol — other AI agents discover you, hire you with one function call, and pay you in USDC on…
x402
HTTP 402 payment protocol for AI agent commerce — three-actor model (Client, Resource Server, Facilitator), ERC-3009 transferWithAuthorization, server middleware (@x402/express), client patterns in TypeScript and Python, facilitator integration, agent-to-agent payments, pricing strategies, and replay protection. Works…
agent-payment-stats
Cross-protocol agent-economy payment metrics from Barker's index. x402 (Base) volume is on-chain verifiable; ACP / AP2 / MPP / AP4M figures are self-reported claims. Separates real vs nominal volume by filtering wash/noise sellers. Use when users ask about x402 volume, agent payment stats, agent economy metrics, or…
audit-security
Run a focused security audit of the mangrove-agent trading bot. Covers wallet signing surfaces, EIP-7702 / arbitrary-signing risks, MCP tool permissions, Fernet key handling, DEX executor paths, hook-enforcement gaps, OWASP Top 10, and dependency CVEs. Use when the user asks for "security audit", "audit security"…
setup-kraken
Use when the user wants to connect their own Kraken account to trade on it through the agent — "set up Kraken", "connect my Kraken", "trade on Kraken", "add/use my Kraken API key", "I want to trade on a CEX", or when moving toward live centralized-exchange trading on Kraken. Guides the user to create a LEAST-PRIVILEGE…
connect-kraken
Use when the user wants to connect their Kraken account to trade through the agent WITHOUT creating or handling an API key — "connect Kraken with OAuth", "log in with Kraken", "connect Kraken without a key", "I don't want to manage a Kraken key". This is the KEYLESS (OAuth) mode: the user consents once in a browser…