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/example-usage)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/example-usage"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/example-usage/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/example-usage"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/example-usage.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.00705 |
| Opus 5 | $0.00000 | $0.00352 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
example-usage 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.
What it actually says
Example Usage
The following Go snippets illustrate how to set up the Temporal worker to listen for tasks defined by this DSL and how to start an instance of a DSL-based workflow.
Worker Setup (dsl/worker/main.go):
This shows the basic setup for a Temporal worker that registers the DSL workflow interpreter (dsl.SimpleDSLWorkflow) and the activities it might invoke (like dsl.SampleActivity1).
package main
import (
"log"
"go.temporal.io/sdk/client"
"go.temporal.io/sdk/worker"
"path/to/your/dsl" // Assuming your DSL package path
)
func main() {
c, err := client.Dial(client.Options{})
if err != nil {
log.Fatalln("Unable to create client", err)
}
defer c.Close()
w := worker.New(c, "dsl-task-queue", worker.Options{})
// Register the DSL workflow interpreter
w.RegisterWorkflow(dsl.SimpleDSLWorkflow)
// Register activities used by the DSL workflows
activities := &dsl.SampleActivities{}
w.RegisterActivity(activities)
// Register other activities...
err = w.Run(worker.InterruptCh())
if err != nil {
log.Fatalln("Unable to start worker", err)
}
}
Workflow Starter (dsl/starter/main.go):
This demonstrates how to start a workflow instance. It typically involves reading a DSL definition (e.g., from a YAML file), parsing it into the dsl.Workflow struct, and then using the Temporal client to execute SimpleDSLWorkflow with that struct.
package main
import (
"context"
"log"
"os"
"github.com/pborman/uuid"
"go.temporal.io/sdk/client"
"gopkg.in/yaml.v3"
"path/to/your/dsl" // Assuming your DSL package path
)
func main() {
// Example: Reading DSL definition from a file (e.g., workflow1.yaml)
dslFilePath := "dsl/workflow1.yaml" // Or get from flag
data, err := os.ReadFile(dslFilePath)
if err != nil {
log.Fatalln("Unable to read DSL file", err)
}
var dslWorkflow dsl.Workflow
err = yaml.Unmarshal(data, &dslWorkflow)
if err != nil {
log.Fatalln("Unable to parse DSL definition", err)
}
c, err := client.Dial(client.Options{})
if err != nil {
log.Fatalln("Unable to create client", err)
}
defer c.Close()
options := client.StartWorkflowOptions{
ID: "dsl-workflow-" + uuid.New(), // Example ID
TaskQueue: "dsl-task-queue",
}
we, err := c.ExecuteWorkflow(context.Background(), options, dsl.SimpleDSLWorkflow, dslWorkflow)
if err != nil {
log.Fatalln("Unable to execute workflow", err)
}
log.Println("Started workflow", "WorkflowID", we.GetID(), "RunID", we.GetRunID())
// Optionally wait for completion
var result []byte
err = we.Get(context.Background(), &result)
if err != nil {
log.Fatalln("Workflow execution failed", err)
}
log.Println("Workflow completed successfully.")
}
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 · 108 lines · 0 tokens per session scan A 416abe18d899
example-usage 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 705 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.