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/vanity-address-generationnpx skills add nirholas/three.ws --skill vanity-address-generationgit 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/vanity-address-generation)<a href="https://agentmods.dev/skills/nirholas/three.ws/vanity-address-generation"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/vanity-address-generation.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.00090 | $0.03393 |
| Opus 5 | $0.00045 | $0.01697 |
| Sonnet 5 | $0.00018 | $0.00679 |
| Haiku 4.5 | $0.00009 | $0.00339 |
Grade A, and why
vanity-address-generation 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 yesterday.
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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vanity Address Generation — From Cryptographic Foundations
This skill teaches you everything about generating custom blockchain addresses — from the elliptic curve math that creates them, to the brute-force algorithms that find patterns, to the security considerations that keep them safe.
What Is a Vanity Address?
A vanity address has a human-chosen pattern in it:
Standard: 0x7a3b9c2d1e4f5a6b8c0d9e2f3a4b5c6d7e8f9a0b
Vanity: 0xSperax... ← starts with "Sperax"
Vanity: 0x...DEAD ← ends with "DEAD"
Vanity: 0x000000... ← leading zeros (gas savings!)
| Use Case | Example | Why |
|---|---|---|
| Brand identity | DAO treasury at 0xSperax... |
Recognizable in block explorers |
| Gas optimization | Contract at 0x000000... |
Leading zeros save gas on calldata |
| Memorability | Personal wallet 0xNick... |
Easy to verify at a glance |
| Security verification | Known prefix for official addresses | Users can spot fakes faster |
| Collectibility | Rare patterns like 0xDEADBEEF... |
Fun, flex, verifiable |
How Addresses Are Born
Ethereum Address Derivation
┌──────────────────────────────────────────────────────┐
│ ETHEREUM ADDRESS DERIVATION │
├──────────────────────────────────────────────────────┤
│ │
│ 1. Generate random 256-bit private key │
│ priv = random_bytes(32) │
│ e.g., 0xac0974bec39a17e36ba4a6b4d238ff944... │
│ │
│ 2. Derive public key via secp256k1 elliptic curve │
│ pub = secp256k1(priv) → 64 bytes (uncompressed)│
│ │
│ 3. Hash public key with Keccak-256 │
│ hash = keccak256(pub) → 32 bytes │
│ │
│ 4. Take last 20 bytes as address │
│ addr = hash[12:] → 20 bytes = 40 hex chars │
│ → 0x followed by 40 hex characters │
│ │
│ priv → secp256k1 → pub → keccak256 → addr │
│ (secret) (ECDSA) (point) (hash) (public) │
│ │
└──────────────────────────────────────────────────────┘
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.
- yesterday First seen · 375 lines · 90 tokens per session scan A 8c1550eeff69
vanity-address-generation is a skill published in the GitHub repository nirholas/three.ws (110 stars, last pushed today), licensed Apache-2.0. It adds 90 tokens to every session and 3,393 once invoked, about $0.0005 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-09-03.
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.