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/mockery)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/mockery"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/mockery/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/mockery"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/mockery.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.01260 |
| Opus 5 | $0.00000 | $0.00630 |
| Sonnet 5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
mockery 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 6d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mockery Mock Generation Rules
Overview
Every interface defined under internal/application/ports/ MUST have a corresponding
mockery-generated mock in the appropriate mocks/ subdirectory of the infrastructure layer.
Manually written mocks or stubs for these interfaces are not allowed.
Placement Convention
Mocks are placed in the infrastructure layer alongside the concrete implementations:
Interface package (application/ports/) |
Mock directory (infrastructure/) |
|---|---|
ports/api/btc/ |
infrastructure/api/btc/mocks/ |
ports/api/eth/ |
infrastructure/api/eth/mocks/ |
ports/api/xrp/ |
infrastructure/api/xrp/mocks/ |
ports/file/ |
infrastructure/storage/file/transaction/mocks/ |
ports/repository/cold/ |
infrastructure/repository/cold/mocks/ |
ports/repository/watch/ |
infrastructure/repository/watch/mocks/ |
Pattern: ports/<layer>/<pkg>/ → infrastructure/<layer>/<pkg>/mocks/
Mandatory Steps When Adding a New Interface
When a new interface is added to internal/application/ports/:
- Add to
.mockery.yaml: Register the interface under its package entry with the correctdir. - Run
make mockery: Regenerate all mocks. - Verify: Run
make go-lintandmake check-build.
Do these in the same commit or PR as the interface definition.
.mockery.yaml Entry Format
packages:
github.com/hiromaily/go-crypto-wallet/internal/application/ports/<layer>/<pkg>:
config:
dir: "internal/infrastructure/<layer>/<pkg>/mocks"
pkgname: "mocks"
interfaces:
MyNewInterface:
Mock File Conventions (auto-applied by global config)
| Setting | Value |
|---|---|
| Filename | mock_<interface_name_snakecase>.go |
| Struct name | Mock<InterfaceName> |
| Constructor | NewMock<InterfaceName>(t) |
| Framework | testify/mock with .EXPECT() builder |
Using Mocks in Tests
import coldmocks "github.com/hiromaily/go-crypto-wallet/internal/infrastructure/repository/cold/mocks"
func TestFoo(t *testing.T) {
repo := coldmocks.NewMockBTCAccountKeyRepositorier(t)
repo.EXPECT().
GetOneMaxID(domainAccount.AccountTypeDeposit).
Return(key, nil)
// ...
}
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.
- 6d ago First seen · 133 lines · 0 tokens per session scan A 6b269c34571d
mockery is a cursor rule 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 1,260 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-03.
Other cursor rules, from other repositories
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
schema_test_implementation_guide
A concise and practical guide for building GoZod Schema test files, updated with the latest practices from stringtest.go, objecttest.go, and complextest.go.
tests-unit
../../.agents/rules/tests-unit.md.
go
Go development guidelines — error handling, concurrency, interfaces, context propagation, and testing. Applied when working with Go code.
go-test
Go test conventions — parallelism, table-driven tests, assertions.
d-test-unit-test
A set of rules for writing unit tests in Go, the programming language used by the examples. It covers test names, table-driven cases, subtests, mocks, assertions, file placement, and basic test quality principles.