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 rules/hiromaily/go-crypto-wallet/e2e-scriptgit 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/e2e-script)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/e2e-script"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/e2e-script.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.00000 | $0.02732 |
| Opus 5 | $0.00000 | $0.01366 |
| Sonnet 5 | $0.00000 | $0.00546 |
| Haiku 4.5 | $0.00000 | $0.00273 |
Grade A, and why
e2e-script 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 3d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BCH E2E Script Development Rules
Rules applied when creating or modifying Bitcoin Cash E2E scripts.
Critical: Read BCH Task Context First
MANDATORY: Before working on any BCH E2E task, read the BCH task context document:
docs/chains/bch/README.md- BCH vs BTC feature differences, workflow comparison, prohibited features
This document explains what BCH can and cannot do compared to BTC.
BCH Protocol Limitations (CRITICAL)
BCH does NOT support the following BTC features:
| Feature | BTC | BCH | Impact |
|---|---|---|---|
| SegWit | Yes | NO | No P2WPKH, P2WSH addresses |
| Taproot | Yes | NO | No P2TR addresses |
| Descriptor | Yes | NO | Cannot use descriptor APIs |
| PSBT | Yes | NO | Use raw transaction hex |
| Schnorr | Yes | NO | ECDSA only |
| MuSig2 | Yes | NO | Traditional multisig only |
| BIP49/84/86 | Yes | NO | BIP44 only |
Required Documentation
Read the following documents before creating or modifying scripts:
| Document | Contents |
|---|---|
docs/chains/bch/README.md |
CRITICAL: BCH vs BTC differences, prohibited features |
docs/chains/bch/README.md |
Detailed BCH technical reference |
scripts/operation/bch/bch_common.sh |
BCH common utility functions |
scripts/operation/common.sh |
Shared utility functions |
BCH Available Patterns
BCH supports only 3 patterns (compared to BTC's 11):
| Pattern | Description | Address Type | Address Format | Signature |
|---|---|---|---|---|
| 1 | P2PKH Single-sig | P2PKH (BIP44) | m.../n... (regtest) |
Single |
| 2 | P2SH 2-of-3 | P2SH | 2... (regtest) |
2-of-3 |
| 3 | P2SH 3-of-3 | P2SH | 2... (regtest) |
3-of-3 |
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.
- 3d ago First seen · 326 lines · 0 tokens per session scan A 02ec53ed4aec
e2e-script 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 2,732 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
solidity
Solidity development standards with Foundry.
wagmi
Web3 integration patterns using Wagmi v2.
viem
Viem v2 integration patterns and Rules.
solidity
Cursor rule "solidity" from devridge0/basilic-evm, covering solidity & foundry rules, core principles, contract structure, foundry testing and gas optimization.
wagmi
Cursor rule "wagmi" from devridge0/basilic-evm, covering wagmi v2 best practices, hooks and state management rules, account connection, smart contract interaction rules and reading from contracts.
viem
Cursor rule "viem" from devridge0/basilic-evm, covering viem v2 rules, core principles, address handling, transaction handling and event handling.