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 hec-ovi/blockchain-skill --skill agent-walletgit clone --depth 1 https://github.com/hec-ovi/blockchain-skillWrote 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/hec-ovi/blockchain-skill/agent-wallet)<a href="https://agentmods.dev/skills/hec-ovi/blockchain-skill/agent-wallet"><img src="https://agentmods.dev/badge/skills/hec-ovi/blockchain-skill/agent-wallet/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/hec-ovi/blockchain-skill/agent-wallet"><img src="https://agentmods.dev/badge/skills/hec-ovi/blockchain-skill/agent-wallet.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00093 | $0.02223 |
| Opus 5 | $0.00046 | $0.01111 |
| Sonnet 5 | $0.00019 | $0.00445 |
| Haiku 4.5 | $0.00009 | $0.00222 |
Grade A, and why
agent-wallet scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Use this CLI only** for wallet/chain ops. Do not quote swaps via random web APIs (0x, Uniswap web, curl to aggregators). `swap-quote` / `swap` on the CLI are the path. This is a copy
100% identical to agent-wallet — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-wallet
Instructions only. Every action is the agent-wallet CLI: one process, JSON envelope {ok, data, error, meta} on stdout, then exit. On ok:false follow error.hint. Keys stay local (keystore v3). No custodial middleman.
Start here
Node >= 22.18. Skill packs ship dist/agent-wallet.mjs (no npm install).
Resolve CLI once (first hit wins; reuse it):
command -v agent-wallet
test -x .noob/skills/agent-wallet/agent-wallet && echo .noob/skills/agent-wallet/agent-wallet
test -f .noob/skills/agent-wallet/dist/agent-wallet.mjs && echo "node .noob/skills/agent-wallet/dist/agent-wallet.mjs"
test -x ./agent-wallet && echo ./agent-wallet
Init once per session:
agent-wallet init
Read data.ready, data.nextActions, data.notes. Do not hand-probe the install.
Passphrase (signing verbs). Do this once, then stop touching it:
- If a
.envat the project root already hasAGENT_WALLET_PASSPHRASE, use it (CLI auto-loads.env). Do not invent another. - Else create
.envonce withAGENT_WALLET_PASSPHRASE=<random >=8 chars>andAGENT_WALLET_HOME=./.agent-wallet-data(or keep default home). Never print the passphrase in chat. - Run verbs from anywhere in the project:
.envis found by walking up, so a scratch subdirectory is fine. - On
PASSPHRASE_WRONG: stop. Do not brute-force, dump keystore JSON, or reverse-engineer the bundle.
Fund testnets by receiving from an external wallet or a public testnet drip site. This toolkit does not drip gas.
When to use which
| Intent | Verb |
|---|---|
| Session ready? | init |
| New / restore wallet | wallet-create / wallet-import |
| Receive address | wallet-addresses |
| Export key / backup secrets | wallet-export (prefer --out) |
| Balance / fees / tx / UTXOs | balance / fees / tx / utxos |
| Pay someone (native, ERC-20, BTC) | send |
| Same-chain token A → B | swap-quote then swap (sell WETH not bare ETH; wrap first if needed) |
| ETH ↔ WETH | wrap / unwrap |
| Unknown contract | contract-learn then call/write |
| Deploy | contract-compile then contract-deploy |
| Chain meta / RPC alive | chain-resolve / chain-check |
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.
- 9d ago First seen · 152 lines · 93 tokens per session scan A 20e134afdc14
agent-wallet is a skill published in the GitHub repository hec-ovi/blockchain-skill (2 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 2,223 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to agent-wallet, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
bch-development
Bitcoin Cash (BCH) API implementation rules. Critical pattern for embedding Bitcoin struct and overriding BCH-specific methods. Use when working on BCH-related code in internal/infrastructure/api/btc/bch/.
wallet-cli
How to run watch, keygen, and sign wallet CLI commands. Use when executing wallet commands or testing wallet functionality.
btc-terminology
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
solidity-development
Solidity smart contract development workflow. Use when modifying smart contracts in apps/eth-contracts/contracts/.
bytesagain-wallet-tracker
Crypto wallet analytics reference — address formats, on-chain analytics, transaction tracing, hardware wallets, and approval revocation.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.