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/index)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/index"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/index/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/index"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/index.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.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
index 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 9d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Temporal DSL for Workflow Definition
A lightweight, declarative DSL in Go for defining Temporal workflows. This approach uses Go structs to represent workflow logic, separating the definition from the activity implementation.
- Declarative: Define workflows using Go structs for
Sequence,Parallel, andActivityInvocation. - Separation of Concerns: Keep workflow logic (
Workflowstruct) separate from activity execution code (Activity methods). - Data Flow: Manage state and pass data between steps using a shared
bindingsmap.
Core DSL Structures
We model the workflow using Go structs defined in the dsl package:
Workflow: Top-level struct holding initialVariablesand theRootStatement.Statement: Represents a single step, containing either anActivityInvocation,Sequence, orParallel.ActivityInvocation: Defines how to call a specific Temporal Activity (Name,Arguments,Result).Sequence: A slice ofStatements executed sequentially.Parallel: A slice ofStatements executed concurrently.
Execution Flow
Workflows defined with this DSL are executed by the SimpleDSLWorkflow function:
- Takes
workflow.Contextand thedsl.Workflowstruct as input. - Initializes a
bindingsmap fromWorkflow.Variables. - Recursively executes the
Statements starting fromRoot. - Uses
workflow.ExecuteActivityto invoke activities based onActivityInvocation. - Handles sequential execution for
Sequenceand concurrent execution (with cancellation) forParallel.
Data Handling (bindings)
- The
bindings map[string]stringacts as the shared state. - Initial values come from
Workflow.Variables. ActivityInvocation.Argumentsspecifies which keys frombindingsprovide input.ActivityInvocation.Resultspecifies the key inbindingsto store the activity's output.
Activity Implementation
- Activities are standard Go functions/methods registered with Temporal (see
activities.mdc). - They accept
context.Contextand input arguments, returning a result and an error. - Use
activity.GetLogger(ctx)for logging within activities. - The DSL invokes activities by their registered string
Name.
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.
- 9d ago First seen · 51 lines · 0 tokens per session scan A c435444c018b
index 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 512 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.
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.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.