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-setupgit 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-setup)<a href="https://agentmods.dev/skills/mission69b/t2000/t2000-setup"><img src="https://agentmods.dev/badge/skills/mission69b/t2000/t2000-setup/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-setup"><img src="https://agentmods.dev/badge/skills/mission69b/t2000/t2000-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 37 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Rogue Agent · line 49 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00113 | $0.03158 |
| Opus 5.5 | $0.00045 | $0.01263 |
| Sonnet 5.5 | $0.00023 | $0.00632 |
| Haiku 4.5 | $0.00011 | $0.00316 |
Grade A, and why
t2000-setup 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
t2000: Agent Wallet — Setup
First: do they even need the CLI?
Marketplace from Claude (or any MCP client) only? Skip everything below.
Add https://mcp.t2000.ai/mcp as a custom connector, approve with Google —
that IS the Passport. No CLI, no skills, nothing local; limits live at
t2000.ai/manage/connections. Details:
the t2000-connect skill.
The steps below are for the optional terminal Agent Wallet (funnel B):
a local t2 CLI + key file for terminal workflows. Connect remains an
optional add-on afterwards.
Purpose
Get a fresh user from "nothing installed" to "Agent Wallet ready" in under 5 minutes, via this skill:
Run `npx skills add mission69b/t2000-skills -s t2000-setup` and follow the
installed skill to set up my Agent Wallet.
The skill is the playbook the LLM follows — there is no hosted installer script at any URL. When invoked, read this file, then execute the steps below in order.
Rules
- Walk the steps in order. Each step depends on the previous one. Skipping breaks setup.
- Stop at the first failure. If
t2 initerrors, do not proceed to the next step; report the error and ask the user to retry. - AI clients connect to the HOSTED MCP — nothing to install. Step 5 adds
https://mcp.t2000.ai/mcpas a connector (OAuth); never write acommand-style t2000 MCP config. - Setup is read + write — show, then ask. Echo each command you're about to run. The user runs it (or confirms you can). Never silently shell out.
- No PIN. No encryption. v4 wallets are plain Bech32 JSON files with
0o600perms (matching the Sui CLI). The user owns the file; back it up viat2 export. - Prime this session for x402 payments. Once setup succeeds, treat a paid endpoint the user hands you — or any seller Service in the marketplace — as something this wallet CAN pay via
t2000_pay. Discover what is listed witht2000_services, then pay. Do not fall back to writing a script for them to run. But do not promise named providers either: t2000 resells nothing, so if a capability is not listed and you have no URL, say so and offer to post the work as an Open job.
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 · 205 lines · 113 tokens per session scan A 95c3a6e819b1
t2000-setup is a skill published in the GitHub repository mission69b/t2000 (23 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 3,158 once invoked, about $0.0005 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
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…
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"…
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…