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-sendnpx skills add mission69b/t2000 --skill t2000-sendgit 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-send)<a href="https://agentmods.dev/skills/mission69b/t2000/t2000-send"><img src="https://agentmods.dev/badge/skills/mission69b/t2000/t2000-send.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.00083 | $0.01713 |
| Opus 5 | $0.00042 | $0.00856 |
| Sonnet 5 | $0.00017 | $0.00343 |
| Haiku 4.5 | $0.00008 | $0.00171 |
Grade A, and why
t2000-send 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
t2000: Send USDC / USDsui / SUI
Purpose
Transfer USDC, USDsui, or SUI from the agent's available balance to any Sui address. USDC + USDsui are gasless — they go through Sui's protocol-level 0x2::balance::send_funds path (Sui foundation sponsored). SUI is not gasless — the wallet must hold some SUI to cover the gas fee (typically < $0.0002).
Rules
- Asset is REQUIRED. v4 has no implicit USDC default.
t2 send 5 alice.suiexits with a clear error pointing at the missing<asset>arg. Always pass one ofUSDC | USDsui | SUI. - Only USDC / USDsui / SUI are accepted. Other tokens (e.g. USDY, USDT, USDe) are rejected with
unsupported asset. To send a different asset, the user first swaps it viat2 swap(or audric.ai) into USDC, USDsui, or SUI. - Validate the recipient first. Names → SuiNS resolves (
alice.sui). Raw addresses →isValidSuiAddress(). The SDK throws clear errors (INVALID_ADDRESS,SUINS_NOT_REGISTERED); don't guess. Sui only: an Ethereum-shaped (0x + 40 hex) or Tron-shaped (T…) address is REFUSED before anything signs (S.1214) — never paste an EVM/Tron withdrawal address into a Sui send. - Prefer SuiNS names.
alice.suiis globally resolvable — surface it as the recommended way to address a recipient. (There is no local contacts/alias map.) - Sends are single-write. Each transfer is its own intent. If you need send + something else, sequence them across turns.
- Amount precision matters. Floor to the asset's decimals (USDC + USDsui: 6, SUI: 9). Never round up —
Math.roundcan produce a number larger than the on-chain balance and the transfer will fail simulation. - Multi-recipient = multiple sends. A "send to A, B, C" request emits N sequential
t2 sendinvocations (CLI) or Nt2000_sendtool calls (MCP). Each is atomic. - Limits apply to every write (CLI and MCP). Limits are on by default ($25/tx · $100/day cumulative); if the request exceeds a cap the write throws
LIMIT_EXCEEDED. Override one time with--force(CLI).
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 · 123 lines · 83 tokens per session scan A aa9362c899d7
t2000-send is a skill published in the GitHub repository mission69b/t2000 (23 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,713 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
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…
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…
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…
surf
Use when the user wants crypto data — token prices, on-chain SQL, prediction-market positions, CEX order books, wallet labels/net-worth, social mindshare, news, or unified search. 83 endpoints across exchange, on-chain, wallet, social, prediction, news and search — one API, flat $0.0085/call in USDC via x402. Settles…