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-test)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/go-test"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/go-test/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-test"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/go-test.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.01295 |
| Opus 5 | $0.00000 | $0.00647 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
go-test 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Test Rules
Overview
Rules for writing and modifying test files (*_test.go) in go-crypto-wallet.
Full reference (SSOT): @docs/guidelines/testing.md
Test File Organization
| Test type | Filename | Package | Build tag |
|---|---|---|---|
| Unit test | *_test.go |
same package (e.g. package btc) |
none |
| Integration test (DB / external) | *_integration_test.go |
external (e.g. package btc_test) |
//go:build integration |
| E2E / complex multi-service | *_test.go in internal/integration_test/ |
package integration_test |
//go:build integration |
// unit_test.go — same package
package btc
// repository_integration_test.go — external package + build tag
//go:build integration
package postgres_test
Test Framework — Mandatory
Always use testify. Never use t.Errorf, t.Fatalf, or reflect.DeepEqual directly.
| Package | When to use |
|---|---|
require |
Fatal — test stops immediately on failure |
assert |
Non-fatal — test continues after failure |
Rule: Use require when subsequent test code depends on the assertion passing; use assert otherwise.
Table-Driven Tests — Mandatory
Always use t.Run with a slice of test cases:
func TestFoo(t *testing.T) {
tests := []struct {
name string
input string
wantErr bool
}{
{"valid", "ok", false},
{"empty", "", true},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
err := Foo(tt.input)
if tt.wantErr {
require.Error(t, err)
} else {
require.NoError(t, err)
}
})
}
}
Mock Usage — Mandatory
Always use mockery-generated mocks. Never write mock structs by hand.
See @.claude/rules/internal/mockery.md for placement convention and exceptions.
Import alias convention:
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 · 185 lines · 0 tokens per session scan A 273835f58e20
go-test 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,295 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
tests-unit
../../.agents/rules/tests-unit.md.
tester
Tester role - Unit, E2E, and visual regression testing.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
typescript-tests
TypeScript and Vitest testing standards for this repo.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.