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/btc-only-files)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/btc-only-files"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/btc-only-files/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/rules/hiromaily/go-crypto-wallet/btc-only-files"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/btc-only-files.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.03420 | $0.03420 |
| Opus 5 | $0.01710 | $0.01710 |
| Sonnet 5 | $0.00684 | $0.00684 |
| Haiku 4.5 | $0.00342 | $0.00342 |
Grade A, and why
btc-only-files 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 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.
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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BCH: BTC-Only Files Warning
⛔ WARNING: YOU ARE ACCESSING A BTC-ONLY FILE
If you are working on a BCH (Bitcoin Cash) task, STOP IMMEDIATELY.
These files contain BTC-specific implementations (PSBT, Descriptor, MuSig2) that are NOT compatible with BCH.
Overview
This rule identifies files that are BTC-ONLY and must NEVER be used, modified, or referenced when working on BCH (Bitcoin Cash) tasks.
Applicable Files (Glob Patterns)
This rule applies when working on any BCH-related task (chain:bch label or BCH keywords in the task).
⛔ COMPLETE LIST OF PROHIBITED FILES FOR BCH
The following 24 files must NEVER be used, modified, or called when working on BCH tasks.
Infrastructure Layer - BTC Only (11 files)
internal/infrastructure/api/btc/btc/psbt.go
internal/infrastructure/api/btc/btc/musig2.go
internal/infrastructure/api/btc/btc/descriptor.go
internal/infrastructure/api/btc/btc/descriptor_service.go
internal/infrastructure/api/btc/btc/descriptor_bech32.go
internal/infrastructure/api/btc/btc/descriptor_info.go
internal/infrastructure/api/btc/btc/descriptor_multisig.go
internal/infrastructure/api/btc/btc/descriptor_p2pkh.go
internal/infrastructure/api/btc/btc/descriptor_p2sh.go
internal/infrastructure/api/btc/btc/descriptor_taproot.go
internal/infrastructure/api/btc/btc/descriptor_taproot_multikey.go
Use Case Layer - BTC Only (13 files)
internal/application/usecase/watch/btc/create_transaction.go
internal/application/usecase/watch/btc/send_transaction.go
internal/application/usecase/watch/btc/import_descriptor.go
internal/application/usecase/watch/btc/musig2_aggregate.go
internal/application/usecase/keygen/btc/sign_transaction.go
internal/application/usecase/keygen/btc/generate_descriptor.go
internal/application/usecase/keygen/btc/export_descriptor.go
internal/application/usecase/keygen/btc/musig2_sign.go
internal/application/usecase/keygen/btc/musig2_nonce.go
internal/application/usecase/keygen/btc/create_musig2_address.go
internal/application/usecase/sign/btc/sign_transaction.go
internal/application/usecase/sign/btc/musig2_sign.go
internal/application/usecase/sign/btc/musig2_nonce.go
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 · 321 lines · 3,420 tokens per session scan A ddd4fe22af2e
btc-only-files is a cursor rule published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 3,420 tokens to every session, about $0.0171 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-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.