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/domain-layer)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/domain-layer"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/domain-layer.svg" alt="Measured on agentmods" 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.00550 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
domain-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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Layer Rules
Overview
Rules for working in the domain layer (internal/domain/).
The domain layer contains pure business logic with ZERO infrastructure dependencies.
Key Principles
- NO dependencies on infrastructure (no database, no API clients, no file I/O)
- Defines interfaces that infrastructure must implement (Dependency Inversion)
- Contains pure business logic testable without mocks
- Most stable layer - changes here affect all other layers
Structure
| Package | Purpose |
|---|---|
account/ |
Account types, validators, multisig configurations |
address/ |
Address entity and types |
auth/ |
Authentication account keys and full public keys |
bitcoin/ |
Bitcoin-specific types (address, transactions, inputs/outputs) |
coin/ |
Cryptocurrency type definitions |
ethereum/ |
Ethereum-specific types (account keys, transactions) |
key/ |
Key value objects, validators, fingerprint, seed |
multisig/ |
Multisig validators, MuSig2 implementation |
payment/ |
Payment request types |
transaction/ |
Transaction entity, types, validators |
wallet/ |
Wallet types, descriptor builder |
xrp/ |
XRP-specific types (constants, account keys) |
Allowed
- Add business rules and validators
- Define value objects and entities
- Create domain interfaces for infrastructure to implement
- Write pure functions (no side effects)
Forbidden
- NEVER import from
infrastructure/,application/, orinterface-adapters/ - NEVER use database, API clients, or file I/O
- NEVER add logging (use
pkg/logger/only if absolutely necessary)
Testing
- Use pure unit tests without mocks
- Test business logic in isolation
- No infrastructure dependencies required
- Tests should be fast and deterministic
Example: Domain Interface
// internal/domain/multisig/nonce_repository.go
// Domain defines the interface, infrastructure implements it
type NonceRepositorier interface {
Store(ctx context.Context, nonce *NonceCommitment) error
GetBySignerAndTx(ctx context.Context, signerID, txID string) (*NonceCommitment, error)
}
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.
- 4d ago First seen · 74 lines · 0 tokens per session scan A b91a09be5255
domain-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 550 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-servemux-rest-api-cursorrules-prompt-file
Cursor rules for Go development with ServeMux REST API integration.
tech-rules
You are an expert AI programming assistant specializing in building APIs with Go, using gin web framework in Go 1.22 or newer. Always use the latest stable version of Go (1.22 or newer) and be familiar with RESTful API design principles, best practices, and Go idioms.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
development_workflow
Spamoor Development Workflow and Best Practices.
typescript
../../.agents/rules/typescript.md.
workflow
This file provides rules and context for generating or understanding Go code related to a custom Domain Specific Language (DSL) for defining Temporal workflows within this project.