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/readme)<a href="https://agentmods.dev/commands/hiromaily/go-crypto-wallet/readme"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/readme/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/readme"><img src="https://agentmods.dev/badge/commands/hiromaily/go-crypto-wallet/readme.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.00496 |
| Opus 5.5 | $0.00000 | $0.00198 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
README 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 1mo 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
Claude Code Commands
Commands
| Command | Description |
|---|---|
/fix-issue #123 |
Work on a GitHub issue |
/fix-linter |
Fix linter errors |
/fix-pr-review #123 |
Address PR review comments |
/recreate-pr #123 |
Copy PR with review comments as fix checklist |
BTC E2E Commands
| Command | Pattern | Description |
|---|---|---|
/e2e/fix-btc-e2e-p1 |
1 | P2PKH Single-sig |
/e2e/fix-btc-e2e-p2 |
2 | P2PKH 2-of-3 Multisig |
/e2e/fix-btc-e2e-p3 |
3 | P2SH-P2WPKH Single-sig |
/e2e/fix-btc-e2e-p4 |
4 | P2SH-P2WSH 2-of-3 Multisig |
/e2e/fix-btc-e2e-p5 |
5 | P2WPKH Native SegWit Single-sig |
/e2e/fix-btc-e2e-p6 |
6 | P2WSH 2-of-3 Multisig |
/e2e/fix-btc-e2e-p7 |
7 | P2WSH 3-of-3 Multisig |
/e2e/fix-btc-e2e-p8 |
8 | P2SH-P2WSH 3-of-3 Multisig |
/e2e/fix-btc-e2e-p9 |
9 | P2TR Taproot Single-sig (in progress) |
Workflow
1. Create Issue 2. Work on Issue
github-issue-creation git-workflow + task skill
↓ ↓
Classify: Type + Lang/Scope Use skill based on label
Assign labels
Related
- Label → Skill mapping: See github-issue-creation
- Git workflow: See git-workflow
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.
- 1mo ago First seen · 40 lines · 0 tokens per session scan A b9e8b6c92343
README is a command published in the GitHub repository hiromaily/go-crypto-wallet (128 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 496 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
compliance-check
Ejecuta todas las verificaciones de compliance de reglas.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
build
A command for carrying out the next unfinished coding task from a plan, including writing tests, implementing the change, checking the project, and committing it. TDD, or test-driven development, means writing a failing test before the code that makes it pass.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
test
Test commit. Use for add tests, update tests, test coverage, unit test, spec.