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-btc-e2e-p4)<a href="https://agentmods.dev/commands/hiromaily/go-crypto-wallet/fix-btc-e2e-p4"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/fix-btc-e2e-p4/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-btc-e2e-p4"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/fix-btc-e2e-p4.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.00386 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
fix-btc-e2e-p4 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 11d 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 BTC E2E Pattern 4 #{issue_number}
Fix errors in BTC E2E test (Pattern 4: P2SH-P2WSH 2-of-3 Multisig).
Prerequisites
MUST read: @.claude/rules/btc/e2e-script.md (common rules, errors, debug commands)
Pattern 4 Specifications
| Item | Value |
|---|---|
| Pattern | 4 - P2SH-P2WSH 2-of-3 Multisig |
| address_type | p2sh-segwit |
| Address Format | 2... (regtest P2SH) |
| Descriptor | sh(wsh(sortedmulti(2,[fp/49'/0'/0']xpub1/0/*,...))) |
| Signature | 2-of-3 |
| Wallets | watch, keygen, sign1, sign2 |
Execution
make btc-e2e-reset P=4
make btc-e2e-verbose P=4
make btc-e2e-cleanup P=4
Pattern-Specific Files
| Type | File |
|---|---|
| Script | scripts/operation/btc/e2e/e2e-p4-p2sh-p2wsh-2of3.sh |
| Account Config | config/wallet/account/account_2of3.yaml |
Signing Flow (2-of-3)
Watch → Keygen (1st) → Sign1 (2nd) → Watch (broadcast)
Git Workflow
When {issue_number} is specified:
- Branch:
fix/btc-e2e-p4-{issue_number} - Commit:
fix(btc): ...
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.
- 11d ago First seen · 47 lines · 0 tokens per session scan A e251fedcc115
fix-btc-e2e-p4 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 386 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.