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/wangqiqi/cursor-ai-rules/go-advancedgit clone --depth 1 https://github.com/wangqiqi/cursor-ai-rulesWrote 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/wangqiqi/cursor-ai-rules/go-advanced)<a href="https://agentmods.dev/rules/wangqiqi/cursor-ai-rules/go-advanced"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/go-advanced.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 | $0.00000 | $0.01683 |
| Opus 5 | $0.00000 | $0.00842 |
| Sonnet 5 | $0.00000 | $0.00337 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
go-advanced 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go 高级实践
本文档是从 @go-basics 分割出来的高级主题部分,涵盖测试策略、性能优化、安全实践和最佳实践。
⚠️ 执行原则
MUST 遵循以下Go高级开发准则:
- MUST 编写全面的单元测试和集成测试
- NEVER 忽略错误处理和边界情况
- ALWAYS 进行性能基准测试
- DO NOT 在生产环境使用调试代码
- MUST 遵循Go语言的安全最佳实践
- ALWAYS 优化goroutine和channel的使用
测试策略
"github.com/yourname/project/internal/repository"
)
// ✅ 推荐:表格驱动测试 func TestUser_Validate(t *testing.T) { tests := []struct { name string user models.User wantErr bool errField string }{ { name: "valid user", user: models.User{ Username: "john_doe", Email: "[email protected]", }, wantErr: false, }, { name: "empty username", user: models.User{ Username: "", Email: "[email protected]", }, wantErr: true, errField: "username", }, { name: "invalid email", user: models.User{ Username: "john_doe", Email: "invalid-email", }, wantErr: true, errField: "email", }, }
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
err := tt.user.Validate()
if tt.wantErr {
assert.Error(t, err)
if tt.errField != "" {
assert.Contains(t, err.Error(), tt.errField)
}
} else {
assert.NoError(t, err)
}
})
}
}
// ✅ 推荐:使用 testify 增强断言 func TestUserService_CreateUser(t *testing.T) { // Setup mockRepo := &repository.MockUserRepository{} service := NewUserService(mockRepo)
// Test data
username := "john_doe"
email := "[email protected]"
// Expectations
expectedUser := &models.User{
Username: username,
Email: email,
}
mockRepo.On("Create", mock.Anything, mock.MatchedBy(func(user *models.User) bool {
return user.Username == username && user.Email == email
})).Return(nil).Once()
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 · 290 lines · 0 tokens per session scan A c1e5f709453a
go-advanced is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (16 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,683 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-08-30.
Other cursor rules, from other repositories
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
code-style
Formatting, lint, comments language.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go
Go conventions for all Zapstore Go projects (zsp, server, zindex, zapstore-cli).