infrastructure-layer

infrastructure-layer is a cursor rule for Cursor from hiromaily/go-crypto-wallet. It costs 0 tokens per session (1,207 once invoked), scanned A, original, MIT.

Rules for the infrastructure layer of a Go cryptocurrency wallet. This layer contains concrete implementations for external APIs, databases, repositories, file storage, and wallet key generation.

In plain words
What is it for?
Use it when adding Bitcoin, Ethereum, or XRP clients, database repositories, file storage, smart-contract utilities, or key-generation code. It also identifies generated database files that should not be edited directly.
Why use it?
It keeps integrations with external systems out of the application and domain layers. The separation makes infrastructure replaceable and prevents implementation details from becoming business rules.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding Bitcoin, Ethereum, or XRP clients, database repositories, file storage, smart-contract utilities, or key-generation code. It also identifies generated database files that should not be edited directly.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/hiromaily/go-crypto-wallet/infrastructure-layer
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.

agentmods badge for infrastructure-layer

README.md
[![agentmods](https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/infrastructure-layer/github.svg)](https://agentmods.dev/rules/hiromaily/go-crypto-wallet/infrastructure-layer)
Your own site
<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/infrastructure-layer"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/infrastructure-layer/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.

agentmods 80×15 button for infrastructure-layer

Your own site · 80×15
<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/infrastructure-layer"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/infrastructure-layer.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,207 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01207
Opus 5 $0.00000 $0.00603
Sonnet 5 $0.00000 $0.00241
Haiku 4.5 $0.00000 $0.00121

Measured 7d ago against content hash c7c9b1c01c02, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

infrastructure-layer 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 7d 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/infrastructure-layer.mdc · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Infrastructure Layer Rules

Overview

Rules for working with the Infrastructure layer (internal/infrastructure/). This layer contains implementations only - no interface definitions.

Structure

internal/infrastructure/
├── api/            # External API clients
│   ├── btc/        # Bitcoin (btc/, bch/, mocks/, testutil/)
│   ├── eth/        # Ethereum (eth/, erc20/, ethtx/, testutil/)
│   └── xrp/        # Ripple (xrp/, mocks/, testutil/)
├── contract/       # Smart contract utilities
├── database/       # SQLC-generated code (DO NOT EDIT)
│   ├── mysql/sqlcgen/
│   └── sqlite/sqlcgen/
├── repository/     # Repository implementations
│   ├── cold/       # Cold wallet (mysql/, sqlite/, mocks/)
│   └── watch/      # Watch wallet (mysql/, sqlite/, mocks/)
├── storage/        # File storage implementations
│   └── file/       # address/, descriptor/, fullpubkey/, transaction/
└── wallet/key/     # Key generation (BIP32, BIP44, BIP84, BIP86, HD wallet)

Critical Principle

Infrastructure contains NO interface definitions.

All interfaces are defined in application/ports/. Infrastructure packages only implement them.

Auto-Generated Files (DO NOT EDIT)

internal/infrastructure/database/mysql/sqlcgen/*.go
internal/infrastructure/database/sqlite/sqlcgen/*.go
internal/infrastructure/api/xrp/xrp/*.pb.go

Type Conversion Pattern

Infrastructure must convert between infrastructure types and domain entities:

// Private conversion functions in repository
func convertToAddress(sqlcAddr *sqlcgen.Address) (*domainAddress.Address, error) {
    return &domainAddress.Address{
        ID:            sqlcAddr.ID,
        CoinTypeCode:  domainCoin.CoinTypeCode(sqlcAddr.Coin),
        AccountType:   domainAccount.AccountType(sqlcAddr.Account),
        WalletAddress: sqlcAddr.WalletAddress,
    }, nil
}

// Public method returns domain entity
func (r *AddressRepositorySqlc) GetAll(...) ([]*domainAddress.Address, error) {
    rows, err := r.queries.GetAllAddresses(...)
    if err != nil {
        return nil, fmt.Errorf("failed to call GetAllAddresses(): %w", err)
    }
    // Convert each row to domain entity
    return convertAll(rows, convertToAddress)
}

Read the full file on GitHub · 141 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.

  1. 7d ago First seen · 141 lines · 0 tokens per session scan A c7c9b1c01c02

Subscribe to this mod's changes

infrastructure-layer 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,207 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.