Rules for generating test mocks from application interfaces with Mockery, a Go tool that creates fake implementations for tests. Each generated mock is placed beside the related infrastructure implementation.

Use it when adding a new application port or updating an existing one. The rules explain where the generated mock goes and what Mockery configuration must be updated.

It gives tests consistent substitutes for APIs, repositories, and file storage without requiring real external systems. It also prevents manually written mocks from drifting away from their interfaces.

mockery — Cursor rule for Cursor by hiromaily/go-crypto-wallet

Install

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.

Clone the repo

git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/mockery/github.svg)](https://agentmods.dev/rules/hiromaily/go-crypto-wallet/mockery)

Your own site

<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.

Your own site · 80×15

<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>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,260 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00000	$0.00504
Sonnet 5.5	$0.00000	$0.00252
Haiku 4.5	$0.00000	$0.00126

Measured 1mo ago against content hash 6b269c34571d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.cursor/rules/internal/mockery.mdc · 133 lines

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 correct dir.
Run make mockery: Regenerate all mocks.
Verify: Run make go-lint and make 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)
    // ...
}

Read the full file on GitHub · 133 lines

Changes

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 · 133 lines · 0 tokens per session scan A 6b269c34571d

Subscribe to this mod's changes

mockery is a cursor rule 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 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.

Go Languages Testing Unit testing bitcoin bitcoin-wallet blockchain erc20 ethereum

mockery

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Mockery Mock Generation Rules

Overview

Placement Convention

Mandatory Steps When Adding a New Interface

`.mockery.yaml` Entry Format

Mock File Conventions (auto-applied by global config)

Using Mocks in Tests

What this file has done since we first saw it

Other cursor rules, from other repositories

gonavi-go

go

code_standards

development_workflow

schema_test_implementation_guide

tests-unit

mockery

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Mockery Mock Generation Rules

Overview

Placement Convention

Mandatory Steps When Adding a New Interface

.mockery.yaml Entry Format

Mock File Conventions (auto-applied by global config)

Using Mocks in Tests

What this file has done since we first saw it

Other cursor rules, from other repositories

gonavi-go

go

code_standards

development_workflow

schema_test_implementation_guide

tests-unit

`.mockery.yaml` Entry Format