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 mission69b/t2000 --skill t2000-receivegit 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-receive)<a href="https://agentmods.dev/skills/mission69b/t2000/t2000-receive"><img src="https://agentmods.dev/badge/skills/mission69b/t2000/t2000-receive/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/mission69b/t2000/t2000-receive"><img src="https://agentmods.dev/badge/skills/mission69b/t2000/t2000-receive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.01575 |
| Opus 5.5 | $0.00028 | $0.00630 |
| Sonnet 5.5 | $0.00014 | $0.00315 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
t2000-receive 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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
t2000: Receive Funds
Purpose
Surface the wallet address (and optionally a Payment Kit URI with a pre-filled amount + memo) so anyone with a Sui wallet can send tokens to the Agent Wallet. Two surfaces:
- CLI (
t2 fund) — prints the wallet address + an ANSI QR code + the value-promise in the terminal. Minimal; no amount or memo. - MCP (
t2000_receive) — returns a JSON payload with the address, an optional Payment Kit URI (sui:pay?…), a nonce, plus an optional amount / currency / memo / label. Use this when the LLM is building a payment-request flow.
Rules
- Receive is non-custodial. The user's address is public; sharing it can't move money — only signed transactions can. Don't add scary disclaimers; the operation is safe.
- Show the QR + the address text. Some users scan, some copy. Both surfaces.
- No PIN, no sign-in. v4 wallets are plain Bech32;
t2 fundis a pure read with no authentication step. - Default currency is USDC. When asking the user to fund the wallet, USDC is the most useful (every paid service is USDC-denominated, USDC sends are gasless). USDsui also works.
- Don't generate a Payment Kit URI without an amount unless asked. A bare address scans just as well; URIs with amounts force the sender into a particular tx shape.
CLI command
t2 fund # address + ANSI QR + share line
t2 fund --qr-only # just the QR (e.g. for embedding in a screenshot)
t2 fund --key <path> # custom wallet path
t2 fund --json # { address, qrEncodedFor, valuePromise }
CLI output (default):
Address 0x55b223b0...0dd1b6
Scan to send tokens to this wallet:
█▀▀▀▀▀█ ▄ ▀▄ █ ▄▀ ▄ █▀▀▀▀▀█
█ ███ █ █ ▀ █ ▄▄ ▀▀ █ ███ █
█ ▀▀▀ █ ▀▄▀▄█▀ ▀▄ ▀▄ █ ▀▀▀ █
▀▀▀▀▀▀▀ ▀ █▀▀ █ ▀ ▀ ▀▀▀▀▀▀▀▀▀
... (truncated)
Or share `0x55b223b0...0dd1b6` directly.
The CLI prints to ANSI — it will look right in any terminal but won't render as image data in MCP responses. Use the MCP tool for a structured JSON response.
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.
- 1mo ago First seen · 115 lines · 71 tokens per session scan A d25b837d54f8
t2000-receive is a skill published in the GitHub repository mission69b/t2000 (23 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,575 once invoked, about $0.0003 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.
Other skills, from other repositories
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…
tenjin-pay
Quote and pay HTTP endpoints that answer 402 Payment Required, with the wallet the tenjin CLI keeps on this machine. tenjin pay --quote reads the price, the payee and the endpoint's advertised request shape for free. tenjin pay pays one call after the user consents to that quote, and -H 'Name: value' sends a header…
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…
basedagents
Register an AI agent on BasedAgents, set a USDC payout wallet, and find, claim, deliver and get paid for tasks. Also post and review tasks as a buyer.