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/fix-bch-e2e-p1)<a href="https://agentmods.dev/commands/hiromaily/go-crypto-wallet/fix-bch-e2e-p1"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/fix-bch-e2e-p1/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/fix-bch-e2e-p1"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/fix-bch-e2e-p1.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.00578 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
fix-bch-e2e-p1 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 10d 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
Fix BCH E2E Pattern 1 #{issue_number}
Fix errors in BCH E2E test (Pattern 1: P2PKH Single-sig).
Prerequisites
MUST read:
- @docs/chains/bch/README.md (CRITICAL: BCH vs BTC differences)
- @.claude/rules/bch/e2e-script.md (common rules, errors, debug commands)
WARNING: BCH does NOT support SegWit, Taproot, Descriptor, PSBT, MuSig2.
Pattern 1 Specifications
| Item | Value |
|---|---|
| Pattern | 1 - P2PKH Single-sig |
| Key Type | BIP44 |
| Address Format | m.../n... (regtest P2PKH) |
| Transaction | Raw TX Hex (NOT PSBT) |
| Signature | Single-sig (ECDSA + SIGHASH_FORKID) |
| Wallets | watch, keygen |
Execution
make bch-e2e-reset P=1
make bch-e2e-verbose P=1
make bch-e2e-cleanup P=1
Pattern-Specific Files
| Type | File |
|---|---|
| Script | scripts/operation/bch/e2e/e2e-p1-p2pkh-singlesig.sh |
| BCH Common | scripts/operation/bch/bch_common.sh |
| Account Config | config/wallet/account/account.yaml |
BCH vs BTC Pattern 1
| Item | BTC Pattern 1 | BCH Pattern 1 |
|---|---|---|
| Descriptor | pkh(...) |
NOT supported |
| Transaction | PSBT | Raw TX Hex |
| Address Import | Descriptor | Address export/import |
| Container | btc-watch |
bch-watch |
BCH-Specific Errors
UTXO Query Issue
# Check balance (watch-only compatible)
docker exec bch-watch bitcoin-cli -regtest -rpcwallet=watch \
getbalance "*" 1 true
Address Format
BCH regtest uses legacy format (m.../n...), not CashAddr.
# Check exported addresses
cat data/address/bch/address_payment_*.csv | head -5
Git Workflow
When {issue_number} is specified:
- Branch:
fix/bch-e2e-p1-{issue_number} - Commit:
fix(bch): ... - Skill: @.claude/skills/git-workflow/SKILL.md
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.
- 10d ago First seen · 76 lines · 0 tokens per session scan A 295112f03126
fix-bch-e2e-p1 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 578 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 commands, from other repositories
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
coverage
Run forge coverage, identify untested branches, generate tests to close gaps.
agent-wallet
Use the bundled agent-wallet skill to operate a non-custodial wallet directly on-chain (EVM and Bitcoin).
krait-fuzz
Run an invariant-based fuzzing campaign: Understand → Extract Invariants → Generate Foundry Tests → Run & Fix Iteratively → Report.
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.