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/repository)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/repository"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/repository/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/repository"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/repository.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.01938 |
| Opus 5 | $0.00000 | $0.00969 |
| Sonnet 5 | $0.00000 | $0.00388 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
repository 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 8d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Pattern
Overview
Rules for implementing Repository pattern in go-crypto-wallet. Repositories abstract data access and map between domain entities and infrastructure.
Applicable Files
internal/application/ports/repository/**/*.go- Interface definitions (Ports)internal/infrastructure/repository/**/*.go- Implementations
Architecture
internal/application/ports/repository/
├── cold/ # Cold wallet repositories (keygen/sign)
│ ├── account_key.go # Interface
│ ├── auth.go
│ └── seed.go
└── watch/ # Watch wallet repositories
├── address.go # Interface
├── btc_transaction.go
└── ...
internal/infrastructure/repository/
├── cold/
│ ├── mysql/ # MySQL implementations
│ │ ├── account_key_sqlc.go
│ │ └── ...
│ └── mocks/ # Test mocks
│ └── mock_*.go
└── watch/
├── mysql/
│ ├── address_sqlc.go
│ └── ...
└── mocks/
└── mock_*.go
Interface Definition (Ports)
Naming Convention
Interface names end with er suffix:
// ✅ GOOD: Descriptive interface names
type AddressRepositorier interface { ... }
type BTCTxRepositorier interface { ... }
type SeedRepositorier interface { ... }
// ❌ BAD: Missing suffix or unclear
type AddressRepository interface { ... }
type AddressRepo interface { ... }
Interface Location
Interfaces MUST be defined in internal/application/ports/repository/:
// internal/application/ports/repository/watch/address.go
package watch
type AddressRepositorier interface {
GetAll(accountType domainAccount.AccountType) ([]*domainAddress.Address, error)
GetAllAddress(accountType domainAccount.AccountType) ([]string, error)
GetOneUnAllocated(accountType domainAccount.AccountType) (*domainAddress.Address, error)
InsertBulk(ctx context.Context, items []*domainAddress.Address) error
UpdateIsAllocated(isAllocated bool, Address string) (int64, 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.
- 8d ago First seen · 309 lines · 0 tokens per session scan A 3083218daceb
repository 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,938 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
trigger
Guidelines for writing PostgreSQL triggers, which are database actions that run automatically when data changes. They explain when a trigger is appropriate and how to keep its function safe and predictable.
rulesforconvex
description: Convex guidelines globs: alwaysApply: true.
startup-migration-bounded-work
Production djangostartup migrate must be bounded; never run makemigrations in production.
redis_rate_limiting
Complete guide for implementing Redis-based rate limiting with authentication troubleshooting and FastAPI integration.
nodejs-mongodb-jwt-express-react-cursorrules-promp
Cursor rules for Node.js development with MongoDB, JWT, Express, and React integration.
web-backend-database-patterns
Best practices for working with databases in backend applications.