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/conventions)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/conventions"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/conventions.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.01599 |
| Opus 5 | $0.00000 | $0.00800 |
| Sonnet 5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
conventions 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go File Rules
Overview
Rules for modifying Go files (*.go) in go-crypto-wallet.
Applicable Directories
| Directory | Description |
|---|---|
internal/ |
Core application code (Clean Architecture) |
pkg/ |
Reusable shared packages |
cmd/ |
Application entry points |
Verification Commands
ALWAYS run before committing:
| Command | Purpose | Required |
|---|---|---|
make go-lint |
Lint and auto-fix | ✅ Yes |
make tidy |
go mod tidy |
✅ Yes |
make check-build |
Build verification (no binary) | ✅ Yes |
make go-test |
Run unit tests | Recommended |
Quick One-Liner
make go-lint && make tidy && make check-build && make go-test
Additional Commands
| Command | Purpose |
|---|---|
make go-fmt |
Format only (gofmt) |
make go-imports |
Format imports |
make go-staticcheck |
Additional static analysis |
make go-check-vuln |
Security vulnerability check |
make go-test-integration |
Integration tests |
Build Rules
CRITICAL: Never run go build directly. Always use Makefile targets.
| Purpose | Command | Output Location |
|---|---|---|
| Verify build (no binary) | make check-build |
/dev/null |
| Build all | make build-all |
${GOPATH}/bin/ |
| Build watch only | make build-watch |
${GOPATH}/bin/watch |
| Build keygen only | make build-keygen |
${GOPATH}/bin/keygen |
| Build sign only | make build-sign |
${GOPATH}/bin/sign{1,2} |
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 · 212 lines · 0 tokens per session scan A 07e7e0c83111
conventions 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,599 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
code_standards
Spamoor Code Standards and Conventions.
development_workflow
Spamoor Development Workflow and Best Practices.
typescript
../../.agents/rules/typescript.md.
typescript
TypeScript coding standards and best practices.
viem
Viem v2 integration patterns and Rules.
typescript
Cursor rule "typescript" from devridge0/basilic-evm, covering typescript rules, core principles, error handling and file structure & organization important.