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.
npx agentmods add rules/hiromaily/go-crypto-wallet/usecasegit 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/usecase)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/usecase"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/usecase.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.01943 |
| Opus 5 | $0.00000 | $0.00971 |
| Sonnet 5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
usecase 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 3d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Rules - Use Case Pattern
Overview
Rules for implementing Use Cases in go-crypto-wallet. Use Cases represent single business operations and are the core of the Application layer.
Applicable Files
internal/application/usecase/**/*.go
Use Case Structure
Interface Definition
Each use case is defined as an interface in the appropriate interfaces.go file:
// ✅ GOOD: Interface with clear single responsibility
type CreateTransactionUseCase interface {
Execute(ctx context.Context, input CreateTransactionInput) (CreateTransactionOutput, error)
}
// ✅ GOOD: Multiple related operations in one interface
type GenerateSeedUseCase interface {
Generate(ctx context.Context) (GenerateSeedOutput, error)
Store(ctx context.Context, input StoreSeedInput) (StoreSeedOutput, error)
}
Implementation Structure
// Private struct (unexported)
type createTransactionUseCase struct {
btcClient apibtc.Bitcoiner // Ports only
addrRepo repowatch.AddressRepositorier
txRepo repowatch.BTCTxRepositorier
// ... other dependencies
}
// Public constructor
func NewCreateTransactionUseCase(
btcClient apibtc.Bitcoiner,
addrRepo repowatch.AddressRepositorier,
txRepo repowatch.BTCTxRepositorier,
// ... pass all dependencies
) watchusecase.CreateTransactionUseCase {
return &createTransactionUseCase{
btcClient: btcClient,
addrRepo: addrRepo,
txRepo: txRepo,
}
}
// Implementation
func (u *createTransactionUseCase) Execute(
ctx context.Context,
input watchusecase.CreateTransactionInput,
) (watchusecase.CreateTransactionOutput, error) {
// Business logic here
}
Method Naming Conventions
| Operation Type | Method Name | Example |
|---|---|---|
| Create/Generate | Execute, Generate, Create |
CreateTransactionUseCase.Execute |
| Read/Get | Get, Find, List |
GetAccountUseCase.Get |
| Update | Update, Modify |
UpdateStatusUseCase.Update |
| Delete | Delete, Remove |
DeleteAccountUseCase.Delete |
| Import/Export | Import, Export |
ImportAddressUseCase.Execute |
| Sign | Sign |
SignTransactionUseCase.Sign |
| Monitor | UpdateTxStatus, MonitorBalance |
MonitorTransactionUseCase.UpdateTxStatus |
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.
- 3d ago First seen · 310 lines · 0 tokens per session scan A 6d20c711d66b
usecase 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,943 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.