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/okx-agent-identitynpx skills add nirholas/three.ws --skill okx-agent-identitygit 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/okx-agent-identity)<a href="https://agentmods.dev/skills/nirholas/three.ws/okx-agent-identity"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/okx-agent-identity.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.00287 | $0.02541 |
| Opus 5 | $0.00143 | $0.01270 |
| Sonnet 5 | $0.00057 | $0.00508 |
| Haiku 4.5 | $0.00029 | $0.00254 |
Grade A, and why
okx-agent-identity 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKX Agent Identity
ERC-8004 agent identity on XLayer (chain fixed — never pass --chain; asked about ETH/BSC/other chains → say identities are created on XLayer only). The CLI does the heavy lifting;
your job: route → confirm → render its output verbatim. You invoke the CLI; the user never sees an onchainos ... literal.
Language Lock (apply on EVERY turn — highest priority, before routing)
The reply language is set by the user's FIRST message in this flow and never drifts. Detect that language once (e.g. Chinese → reply in Chinese; English → reply in English) and answer in it for the entire conversation — every prompt, card, finding, confirm footer, and post-success line. Switch only if the user themselves switches language.
- Every template, card, footer, and prompt in this SKILL.md and all
references/*.mdis authored in English as a STRUCTURE GUIDE, not literal output. Before sending, translate all of it into the locked language. "Render verbatim" in the references means preserve the layout, fields, and meaning — it does NOT mean keep the English words. - Verbatim-keep ONLY:
#ids, wallet addresses, tx hashes, raw tokens/enums the user typed, and CDN URLs. Everything else — including CLI*Labelfields and placeholder strings (per invariants.md) — is translated. - Re-anchor each turn: before composing any message, restate to yourself the locked language and write in it. If you catch yourself echoing an English template line, translate it first. One mixed-language reply is a defect.
Routing (do this FIRST, before loading any reference)
Negative triggers → route OUT in business language only (never name a skill, never show an onchainos ... literal):
- publish / accept / deliver / dispute / negotiate a task → okx-agent-task
- "I want to be an evaluator" with no register word → ask once: 1. Register an Evaluator Agent identity / 2. Open a dispute on a task → route on the reply.
Identity-not-wallet: "再建一个买家身份 / 再加一个用户 / add another agent / new ASP / add another User / new Client" = ALWAYS an identity, NEVER wallet add (covers every role alias — User / 用户 / Buyer / Client / ASP / 卖家 …, not just the examples shown). Finding marketplace agents → run agent search, never list skill names. Passive onboarding (need-user from a task flow) → register user only.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 121 lines · 287 tokens per session scan A c272c5347906
okx-agent-identity is a skill published in the GitHub repository nirholas/three.ws (110 stars, last pushed today), licensed Apache-2.0. It adds 287 tokens to every session and 2,541 once invoked, about $0.0014 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
blockchain-cross-chain
Cross-chain protocols, IBC, LayerZero, Wormhole, Axelar, CCIP, bridges, atomic composability, shared sequencer, cross-chain message passing. Covers trust models (light clients, external validators, ZK proofs), bridge security, token representation (canonical, wrapped, native), relayer economics, and cross-chain…
blockchain-security
Use this skill when asked about blockchain security, smart contract auditing, DeFi threat modeling, blockchain incident response, bug bounty programs, economic security, formal verification of smart contracts, and blockchain-specific security analysis. Languages: Solidity, Python, Rust, Haskell. Covers threat modeling…
blockchain-testing
Use this skill when asked about testing smart contracts, Foundry tests, Hardhat tests, fuzz testing, invariant testing, property-based testing, formal verification, audit preparation, integration testing for dApps, and blockchain testing patterns. Covers Foundry cheatcodes, Echidna fuzzing, Certora verification…
xpr-network-dev
XPR Network (formerly Proton) blockchain development - proton-tsc smart contracts, @proton CLI and web SDK, RPC and Hyperion queries, DeFi (MetalX, Alcor, LOAN), NFTs, the XPR Agents job board, node and Hyperion operations. Use for anything mentioning XPR, Proton, or @proton packages.
blockchain-management
Use this skill when asked about blockchain project management, DAO governance, multi-sig operations, treasury management, tokenomics design, and web3 project methodology. Languages: Solidity, TypeScript, Python. Covers DAO governance frameworks (Compound Governor, Aave, Snapshot, Tally), multi-sig wallet operations…
modernize-move
Detects and modernizes outdated Move V1 syntax, patterns, and APIs to Move V2+. Use when upgrading legacy contracts, migrating to modern syntax, or converting old patterns to current best practices. NOT for writing new contracts (use write-contracts) or fixing bugs.