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.
git clone --depth 1 https://github.com/hiromaily/go-crypto-walletWrote 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/commands/hiromaily/go-crypto-wallet/sign-wallet)<a href="https://agentmods.dev/commands/hiromaily/go-crypto-wallet/sign-wallet"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/sign-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/commands/hiromaily/go-crypto-wallet/sign-wallet"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/sign-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.00000 | $0.00560 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
sign-wallet 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 8d 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.
What it actually says
Sign Wallet Commands
Sign Wallet operates offline as a cold wallet. It provides subsequent signatures (2nd, 3rd, etc.) for multisig transactions. Each authorization operator uses their own Sign Wallet instance.
Create Commands
sign create seed
Creates a seed for the authorization account wallet. If --seed is provided, it will be stored instead of
generating a new one.
Options:
--seed <string>- Seed value to store (development use only)
Example:
sign create seed
sign create hdkey
Creates HD keys for the authorization account.
Example:
sign create hdkey
Export Commands
sign export fullpubkey
Exports full public key addresses as a CSV file for import into Keygen Wallet. These are used to create multisig addresses.
Example:
sign export fullpubkey
Import Commands
sign import privkey
Imports generated private keys for the authorization account into the database.
Example:
sign import privkey
Sign Commands
sign sign signature
Signs a transaction that has already been signed by Keygen Wallet (or other Sign Wallets). This provides subsequent signatures for multisig addresses.
Options:
--file <path>- Path to the signed transaction file
Example:
sign sign signature --file data/tx/btc/tx_signed1_1234567890.json
API Commands
API commands are coin-specific and dynamically configured based on the --coin flag.
Bitcoin/Bitcoin Cash API (sign api with --coin btc or --coin bch)
sign api encryptwallet- Encrypts the wallet with a passphrase--passphrase <string>- Passphrase for encryption
sign api walletpassphrase- Stores the wallet decryption key in memory--passphrase <string>- Passphrase to unlock the wallet
sign api walletpassphrasechange- Changes the wallet passphrase--old <string>- Old passphrase--new <string>- New passphrase
sign api walletlock- Locks the wallet by removing the encryption key from memory
Ethereum API (sign api with --coin eth)
sign api clientversion- Get client versionsign api nodeinfo- Get node informationsign api syncing- Get synchronization statussign api netversion- Get network version
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.
- 8d ago First seen · 95 lines · 0 tokens per session scan A 19b5f722e975
sign-wallet is a command published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 560 tokens. 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 commands, from other repositories
agent-wallet
Use the bundled agent-wallet skill to operate a non-custodial wallet directly on-chain (EVM and Bitcoin).
CLAUDE
Command "CLAUDE" from Calhooon/bsv-wallet-cli, covering commands, files, decisions, gotchas and related.
audit
Full security audit of a Solidity/Vyper/Rust contract or directory. Runs the entire vuln-skills library and dispatches DeFi specialist subagents based on detected protocol type.
audit-live
Audit a deployed contract on a live chain. Pulls verified source from the block explorer, optionally forks the chain for live-state simulation.
audit-multi-chain
Diff the on-chain configuration of one contract deployed across multiple chains — owner, oracle, fees, timelock, pause state, proxy impl — and flag the chain that drifted.
exploit
Generate a working Foundry PoC that exploits a specific finding. Compiles and passes.