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/compozy/gographWrote 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/compozy/gograph/core-libraries)<a href="https://agentmods.dev/rules/compozy/gograph/core-libraries"><img src="https://agentmods.dev/badge/rules/compozy/gograph/core-libraries/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/compozy/gograph/core-libraries"><img src="https://agentmods.dev/badge/rules/compozy/gograph/core-libraries.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.00515 | $0.00515 |
| Opus 5.5 | $0.00206 | $0.00206 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
core-libraries 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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Libraries & Project Utilities
Required Libraries
<library_requirements type="web_framework"> Web Framework:
- MUST use:
gin-gonic/ginfor HTTP APIs </library_requirements>
<library_requirements type="database"> Database:
- PostgreSQL:
jackc/pgx/v5 - Redis:
redis/go-redis/v9 - Always use connection pooling and proper cleanup </library_requirements>
<library_requirements type="testing"> Testing:
- MUST use:
stretchr/testifyfor assertions and mocks - Import as:
github.com/stretchr/testify/assert,github.com/stretchr/testify/mock - STANDARDIZE: Replace all custom mocks with
testify/mockimplementations </library_requirements>
<library_requirements type="validation"> Validation:
- MUST use:
go-playground/validator/v10for input validation </library_requirements>
<library_requirements type="logging"> Logging:
- MUST use:
charmbracelet/log - NEVER use:
fmt.Printforlog.Printffor application logging </library_requirements>
<library_requirements type="cli"> CLI:
- MUST use:
spf13/cobrafor commands </library_requirements>
<library_requirements type="documentation"> Documentation:
- MUST use:
swaggo/swagfor API documentation </library_requirements>
Project Utilities
<utility_pattern type="core_types">
// Use project core types
var taskID core.ID // UUIDs
var reference core.Ref // Polymorphic references
</utility_pattern>
<utility_pattern type="test_helpers">
// Use project test utilities
func TestService(t *testing.T) {
t.Run("Should setup test environment", func(t *testing.T) {
db := utils.SetupTest()
defer db.Close()
fixture := utils.SetupFixture("user_data.json")
// test implementation
})
}
</utility_pattern>
<utility_pattern type="template_engine">
// Use pkg/tplengine for dynamic configurations
engine := tplengine.New()
result, err := engine.Process(template, variables)
</utility_pattern>
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.
- 1mo ago First seen · 82 lines · 515 tokens per session scan A 95f5629509b0
core-libraries is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It adds 515 tokens to every session, about $0.0021 per session on Opus 5.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
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
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-servemux-rest-api-cursorrules-prompt-file
Cursor rules for Go development with ServeMux REST API integration.
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.
usecase
Claude Rules - Use Case Pattern.