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/go-path)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/go-path"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/go-path/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/go-path"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/go-path.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.00373 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
go-path 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 5d 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.
What it actually says
Go Path Configuration Rules
Overview
This project uses Homebrew-installed Go only. Version managers (e.g., mise, asdf, goenv) must NOT affect this project.
Required Go Version
The Go version is specified in go.mod. Always use the Homebrew-installed Go that matches this version.
Common Symptoms of Version Manager Interference
compile: version "go1.X.X" does not match go tool version "go1.Y.Y"go versionshows different version than expected- Build failures after Go upgrade
Diagnosis
# Check which Go is being used
which go
go version
go env GOROOT
# Check for version managers in PATH (should NOT be present)
echo $PATH | tr ':' '\n' | grep -E 'mise|asdf|goenv'
Solution: Disable Version Managers
If a version manager is interfering, remove it from PATH for this session:
# Remove version managers from PATH and use Homebrew Go
export PATH=$(echo $PATH | tr ':' '\n' | grep -v 'mise' | tr '\n' ':' | sed 's/:$//')
export GOROOT=/opt/homebrew/Cellar/go/1.26.2/libexec
# Verify
go version
Expected Environment
| Variable | Expected Value |
|---|---|
which go |
/opt/homebrew/bin/go |
go version |
Matches go.mod version |
GOROOT |
/opt/homebrew/Cellar/go/<version>/libexec |
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.
- 5d ago First seen · 56 lines · 0 tokens per session scan A 4b765e94b3a4
go-path 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 373 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.