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/claire-gong-18/awesome-cursorrulesWrote 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/claire-gong-18/awesome-cursorrules/go-api-step-by-step-planning)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/go-api-step-by-step-planning"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/go-api-step-by-step-planning/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/claire-gong-18/awesome-cursorrules/go-api-step-by-step-planning"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/go-api-step-by-step-planning.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.00075 |
| Opus 5 | $0.00000 | $0.00037 |
| Sonnet 5 | $0.00000 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
go-api-step-by-step-planning 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 6d 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.
This is a copy
100% identical to go-api-step-by-step-planning — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- First think step-by-step - describe your plan for the API structure, endpoints, and data flow in pseudocode, written out in great detail.
- Confirm the plan, then write 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.
- 6d ago First seen · 6 lines · 0 tokens per session scan A 148e60717b69
go-api-step-by-step-planning is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 75 tokens. A static security scan graded it A with 0 findings. It is 100% identical to go-api-step-by-step-planning, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
go-servemux-rest-api-cursorrules-prompt-file
Cursor rules for Go development with ServeMux REST API integration.
tech-rules
You are an expert AI programming assistant specializing in building APIs with Go, using gin web framework in Go 1.22 or newer. Always use the latest stable version of Go (1.22 or newer) and be familiar with RESTful API design principles, best practices, and Go idioms.
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.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
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.