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/nirholas/three.ws/pay-for-servicenpx skills add nirholas/three.ws --skill pay-for-servicegit clone --depth 1 https://github.com/nirholas/three.wsWrote 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/nirholas/three.ws/pay-for-service)<a href="https://agentmods.dev/skills/nirholas/three.ws/pay-for-service"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/pay-for-service.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.00132 | $0.01449 |
| Opus 5 | $0.00066 | $0.00724 |
| Sonnet 5 | $0.00026 | $0.00290 |
| Haiku 4.5 | $0.00013 | $0.00145 |
Grade A, and why
pay-for-service 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.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Making Paid x402 Requests
Use the npx [email protected] x402 pay command to call paid API endpoints with automatic USDC payment on Base.
Which payment stack (arbitration)
three.ws runs two x402/payment stacks. Pick one deterministically — never settle a payment through a signing path the user didn't ask for:
- This stack (awal / three.ws-native) — the default. Use it for a plain x402 402 that settles with a one-shot USDC-on-Base payment.
- OKX
onchainosstack (okx-agent-payments-protocol) — use only when the user names OKX/OnchainOS, or the 402 is one OKX handles specifically: a payment channel / voucher / session,permit2,upto/metered billing, MPP charge, or an a2a-paypaymentId. Hand off there and do not pay from here.
Confirm wallet is initialized and authed
npx [email protected] status
If the wallet is not authenticated, refer to the authenticate-wallet skill.
Command Syntax
npx [email protected] x402 pay <url> [-X <method>] [-d <json>] [-q <params>] [-h <json>] [--max-amount <n>] [--json]
Options
| Option | Description |
|---|---|
-X, --method <method> |
HTTP method (default: GET) |
-d, --data <json> |
Request body as JSON string |
-q, --query <params> |
Query parameters as JSON string |
-h, --headers <json> |
Custom HTTP headers as JSON string |
--max-amount <amount> |
Max payment in USDC atomic units (1000000 = $1.00) |
--correlation-id <id> |
Group related operations |
--json |
Output as JSON |
USDC Amounts
X402 uses USDC atomic units (6 decimals):
| Atomic Units | USD |
|---|---|
| 1000000 | $1.00 |
| 100000 | $0.10 |
| 50000 | $0.05 |
| 10000 | $0.01 |
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.
- 5d ago First seen · 116 lines · 132 tokens per session scan A 557fc7d950c6
pay-for-service is a skill published in the GitHub repository nirholas/three.ws (110 stars, last pushed yesterday), licensed Apache-2.0. It adds 132 tokens to every session and 1,449 once invoked, about $0.0007 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
rtc-balance
Check RustChain wallet balance, epoch info, and network status via the public RPC.
blockchain-defi
Use this skill when asked about decentralized finance, DeFi protocols, AMM mechanics, lending and borrowing protocols, perpetual futures, yield farming, liquidity mining, liquid staking, restaking, yield optimization, DeFi security, MEV, and protocol composability. Covers AMM design (Uniswap, Curve, Balancer), lending…
apex-copilot
Use this skill when the user is working on a Web3 project and needs Apex Foundation diligence tools: scoring a crypto/Web3 project for investment readiness, matching against the Apex portfolio of 200+ projects, finding relevant Web3 hackathons, matching against Web3 VC funds and investors, smart contract code review…
stablecoin-chain-explorer
Explore stablecoin TVL distribution and yield opportunities by blockchain. Query which chains have the most stablecoins, compare cross-chain yields, and find the best opportunities on Ethereum, BSC, Arbitrum, Base, Polygon, and more. Also for protocols and issuers researching where stablecoin TVL and liquidity…
gstd-sovereign
Full agent autonomy — self-sustaining economic entity that earns GSTD, manages finances, shares intelligence, recruits agents, and promotes financial independence.
crypto-report
Analyze cryptocurrency projects with tokenomics, on-chain metrics, and market analysis. Generate comprehensive crypto research reports.