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.
npx agentmods add rules/golid-ai/golid/frontend-libgit 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/frontend-lib)<a href="https://agentmods.dev/rules/golid-ai/golid/frontend-lib"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/frontend-lib.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00950 |
| Opus 5 | $0.00000 | $0.00475 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
frontend-lib 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Lib Patterns
Thesis: Lib files are the shared foundation: typed API client, auth store, constants, and utilities. Every API call is typed, every protected route is registered.
Follow the established patterns in api.ts, auth.ts, and constants.ts.
API Client (api.ts)
Adding a New API Module
Group types and methods together. Follow the established API object pattern:
// 1. Define TypeScript interfaces matching backend response structs
export interface Item {
id: string;
title: string;
// ... fields match the Go Detail struct exactly
}
export interface ItemListResult {
items: Item[];
total: number;
page: number;
per_page: number;
total_pages: number;
}
// 2. Query builder for list endpoints (if filterable)
function buildItemQuery(params?: ItemListParams): string { ... }
// 3. API object with typed methods
export const itemsApi = {
create: (data: CreateItemInput) => post<Item>("/items", data),
list: (params?: ItemListParams) => get<ItemListResult>(`/items${buildItemQuery(params)}`),
getById: (id: string) => get<Item>(`/items/${id}`),
update: (id: string, data: Partial<Item>) => put<Item>(`/items/${id}`, data),
delete: (id: string) => del<{ message: string }>(`/items/${id}`),
};
Conventions
- Use the convenience helpers —
get,post,put,patch,delfrom the same file. Never rawfetch. - Type every response —
get<MyType>(...)notget<any>(...). - All endpoints start with
/— theapi()function prepends/api/v1. skipAuth: trueonly for public endpoints (login, register, universities).- Optional fields use
?— match the Go struct'somitemptytags.
Search/Filter Query Builder
For list endpoints with search and pagination, use a query builder function:
function buildItemQuery(params?: { page?: number; perPage?: number; search?: string }): string {
const p = new URLSearchParams();
if (params?.page) p.set("page", String(params.page));
if (params?.perPage) p.set("per_page", String(params.perPage));
if (params?.search) p.set("search", params.search);
const qs = p.toString();
return qs ? `?${qs}` : "";
}
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.
- 5d ago First seen · 102 lines · 0 tokens per session scan A 57cd02bfe83e
frontend-lib is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 950 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
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
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.
core
Core token-efficiency and response discipline rules. Always active.