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/verify-e2e-flow)<a href="https://agentmods.dev/commands/hiromaily/go-crypto-wallet/verify-e2e-flow"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/verify-e2e-flow/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/verify-e2e-flow"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/verify-e2e-flow.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.00983 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
verify-e2e-flow 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 8d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify E2E flow $ARGUMENTS
Verify that the E2E scripts for the specified chain follow the documented transaction flow.
Usage
/e2e:verify-e2e-flow btc
/e2e:verify-e2e-flow eth
/e2e:verify-e2e-flow xrp
/e2e:verify-e2e-flow bch
/e2e:verify-e2e-flow all
Reference Documents
MUST read first:
docs/transaction-flow.md— canonical 3-wallet flow (Watch / Keygen / Sign) and transaction lifecycle
Chain-specific (load based on argument):
| Chain | Scripts Directory | Chain Doc |
|---|---|---|
btc |
scripts/operation/btc/e2e/ |
docs/chains/btc/README.md |
eth |
scripts/operation/eth/e2e/ |
docs/chains/eth/README.md |
xrp |
scripts/operation/xrp/e2e/ |
docs/chains/xrp/README.md |
bch |
scripts/operation/bch/e2e/ |
docs/chains/bch/README.md |
all |
All of the above | All of the above |
Verification Steps
Step 1: List all e2e scripts
Use Glob to list all scripts in scripts/operation/{chain}/e2e/*.sh (excluding parallel runner).
Step 2: Read each script
Read all pattern scripts (not e2e-parallel-runner.sh).
Step 3: Check each script against the documented flow
For each script, verify the following phases are present and correct:
Setup Flow
Single-sig patterns:
- Keygen:
create seed - Keygen:
create hdkey(for all required accounts) - Keygen: export address / descriptor
- Watch: import address / descriptor
Multisig patterns (additional steps):
- Sign wallet(s):
create seed - Sign wallet(s):
create hdkey - Sign wallet(s):
export fullpubkey - Keygen:
import fullpubkey(for each sign wallet)
Transaction Flow
- Watch:
create [payment|transfer|deposit]→ produces unsigned tx file - Keygen:
sign signature --file <unsigned_tx>→ produces signed/partial tx file - Sign wallet(s):
sign signature --file <partial_tx>(multisig only, repeated until threshold met) - Watch:
send tx --file <signed_tx>→ broadcasts and returns txID
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.
- 8d ago First seen · 107 lines · 0 tokens per session scan A 03e770bd9c33
verify-e2e-flow 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 983 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.