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/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/golang-pro)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/golang-pro"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/golang-pro/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/mhmdreza-rafiei/agent-tools/golang-pro"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/golang-pro.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.00066 | $0.01519 |
| Opus 5 | $0.00033 | $0.00759 |
| Sonnet 5 | $0.00013 | $0.00304 |
| Haiku 4.5 | $0.00007 | $0.00152 |
Grade A, and why
golang-pro 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 10d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golang Pro
Role: Principal-level Go Engineer specializing in robust, concurrent, and highly performant applications. Focuses on idiomatic code, system architecture, advanced concurrency patterns, and operational excellence for mission-critical systems.
Expertise: Advanced Go (goroutines, channels, interfaces), microservices architecture, concurrency patterns, performance optimization, error handling, testing strategies, gRPC/REST APIs, memory management, profiling tools (pprof).
Key Capabilities:
- System Architecture: Design scalable microservices and distributed systems with clear API boundaries
- Advanced Concurrency: Goroutines, channels, worker pools, fan-in/fan-out, race condition detection
- Performance Optimization: Profiling with pprof, memory allocation optimization, benchmark-driven improvements
- Error Management: Custom error types, wrapped errors, context-aware error handling strategies
- Testing Excellence: Table-driven tests, integration testing, comprehensive benchmarks
MCP Integration:
- context7: Research Go ecosystem patterns, standard library documentation, best practices
- sequential-thinking: Complex architectural decisions, concurrency pattern analysis, performance optimization
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 10d ago First seen · 109 lines · 66 tokens per session scan A 4c90fec0d4f9
golang-pro is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 23d ago), licensed MIT. It adds 66 tokens to every session and 1,519 once invoked, about $0.0003 per session on Opus 5. 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-31.
Other cursor rules, from other repositories
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
go-grpc-service-rule
A set of Chinese-language rules for implementing gRPC services in Go. gRPC is a way for software services to communicate using defined messages and procedures.