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/golid-ai/golidWrote 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/golid-ai/golid/write-tests)<a href="https://agentmods.dev/rules/golid-ai/golid/write-tests"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/write-tests/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/golid-ai/golid/write-tests"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/write-tests.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.01267 |
| Opus 5.5 | $0.00000 | $0.00507 |
| Sonnet 5.5 | $0.00000 | $0.00253 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
write-tests 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Backend Tests
Thesis: Test the contract, not the implementation. Integration tests hit real PostgreSQL; unit tests are table-driven; every service method has error path coverage.
Before writing tests for a module, read docs/modules/{module}/spec.md
for the Critical Test Scenarios section — it's a verified test plan.
Integration Tests (Service Layer)
Test real SQL against a real PostgreSQL instance using testutil.WithTestDB.
//go:build integration
package service_test
import (
"testing"
"github.com/golid-ai/golid/backend/internal/service"
"github.com/golid-ai/golid/backend/internal/testutil"
)
func TestItemService_Create(t *testing.T) {
testutil.WithTestDB(t, func(pool *pgxpool.Pool) {
svc := service.NewItemService(pool, 20, 100)
// Seed prerequisite data with raw SQL
_, err := pool.Exec(ctx, `INSERT INTO users (...) VALUES (...)`)
// ...
// Test the service method
result, err := svc.Create(ctx, &service.CreateItemInput{...})
if err != nil { t.Fatalf("expected no error, got %v", err) }
if result.Title != "Test Item" { t.Errorf("expected title 'Test Item', got %s", result.Title) }
})
}
Key Rules
- Build tag:
//go:build integrationat the top of the file. - File naming:
x_integration_test.go(notx_test.go) to make it clear. - Seed with raw SQL: Use
pool.Execwith INSERT statements. Never use service methods to seed — they have their own validation and side effects. - Test one thing per function: Each test function should test one behavior (happy path, error case, permission check, etc.).
- Clean state:
WithTestDBprovides a fresh database for each test. No cleanup needed.
What to Test
- Happy paths: Create, Read, Update, Delete with valid inputs.
- Permission checks: Wrong user type, non-owner, non-member. Expect
FORBIDDEN. - Status guards: Operation on wrong-status parent. Expect
BAD_REQUEST. - Not found: Non-existent ID. Expect
NOT_FOUND. - Conflict: Duplicate entries. Expect
CONFLICT. - Edge cases: Empty arrays, null optional fields, boundary values.
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 · 131 lines · 0 tokens per session scan A b839c032001c
write-tests is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,267 tokens. 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-30.
Other cursor rules, from other repositories
rails-cursorrules-prompt-file
Cursor rules for Rails development with basic setup.
architecture
This document outlines the fundamental architectural principles and patterns for the mcp-debug codebase. Adherence to these guidelines is mandatory to maintain a clean, decoupled, and testable system.
testing
Vitest toolchain and testing discipline - two runtimes, no watch for agents, authoring gate, junk patterns.
unit-tests-tdd
TDD for behavior changes; co-located tests; keep touched areas well covered.
api
For creating tests for the backend in bubblelab-api.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.