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/rules/hiromaily/go-crypto-wallet/3rd-library)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/3rd-library"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/3rd-library.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.1 | $0.00000 | $0.01695 |
| Opus 5 | $0.00000 | $0.00847 |
| Sonnet 5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
3rd-library 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 7d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XRP Third-Party Library Rules
Overview
This project uses two separate XRP Go libraries for distinct purposes.
The official XRPL documentation recommends github.com/XRPLF/xrpl-go, but this project does not use that library.
Do not confuse the three libraries — their module paths are different and they are not interchangeable.
Library Summary
| Library | Module Path | Version | Purpose |
|---|---|---|---|
| Peersyst xrpl-go | github.com/Peersyst/xrpl-go |
v0.1.15 | Offline signing, address codec, binary codec |
| XRPScan xrpl-go | github.com/xrpscan/xrpl-go |
v0.2.11 | WebSocket client for XRPL node communication |
github.com/XRPLF/xrpl-go |
— | NOT USED in this project |
Library 1: github.com/Peersyst/xrpl-go — Offline Cryptographic Operations
What it does
Provides offline (no-network) XRP Ledger cryptographic operations:
- Binary codec (
binary-codec): canonical serialization of XRP transaction objects - Address codec (
address-codec): Base58Check encoding/decoding of XRP addresses and seeds - Wallet (
xrpl/wallet): key pair derivation from seed, transaction signing
Where it is used in this project
| File | Package Used | Purpose |
|---|---|---|
pkg/chains/xrp/hash.go |
address-codec |
Base58CheckEncode/Decode for seed encoding |
pkg/chains/xrp/sign.go |
address-codec |
Seed decoding in decodeSeed() and DetectAlgorithmFromSeed() |
internal/infrastructure/api/xrp/signer/peersyst_signer.go |
binary-codec, xrpl/wallet |
Transaction serialization and signing in PeersystSigner |
When to use it
- Any offline cryptographic operation: signing, serialization, seed/address encoding
- Implementing or extending
TransactionSigner(internal/application/ports/api/xrp/transaction_signer.go) - Extending
pkg/chains/xrp/utilities (hash, sign, keygen)
Key types and packages
import addresscodec "github.com/Peersyst/xrpl-go/address-codec"
import binarycodec "github.com/Peersyst/xrpl-go/binary-codec"
import xrplwallet "github.com/Peersyst/xrpl-go/xrpl/wallet"
// Address encoding
encoded, err := addresscodec.Base58CheckEncode(bytes, prefix)
decoded, err := addresscodec.Base58CheckDecode(str)
// Transaction signing
wallet, err := xrplwallet.FromSeed(seed, "")
txBlob, err := binarycodec.Encode(txMap)
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.
- 7d ago First seen · 156 lines · 0 tokens per session scan A 948b21015e30
3rd-library is a cursor rule 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 1,695 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-01.
Other cursor rules, from other repositories
viem
Viem v2 integration patterns and Rules.
code_standards
Spamoor Code Standards and Conventions.
10-naming
An open repository of EVM-compatible wallets 🌸.
typescript
../../.agents/rules/typescript.md.
solidity
Solidity development standards with Foundry.
wagmi
Web3 integration patterns using Wagmi v2.