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-componentsgit 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-components)<a href="https://agentmods.dev/rules/golid-ai/golid/frontend-components"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/frontend-components.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.00723 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
frontend-components 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Creation Patterns
Thesis: Components are stateless building blocks. Atoms compose into molecules, molecules into organisms. Every component exports from the barrel.
Reference files: Button.tsx (atom) and Modal.tsx (molecule).
Atom vs Molecule vs Organism
- Atom: No dependencies on other components. Self-contained. (Button, Input, Chip, Avatar, StarRating)
- Molecule: Composes atoms. (Card, Modal, Tabs, Dropzone, Select, DestructiveModal)
- Organism: Composes molecules + atoms into a page section. (Navbar, Sidebar, Footer)
File Structure
components/
├── atoms/
│ └── NewComponent/
│ └── NewComponent.tsx
├── molecules/
│ └── NewComponent/
│ └── NewComponent.tsx
├── organisms/
│ └── NewComponent.tsx
└── index.ts ← MUST export here
Component Template
import { type Component, splitProps, Show } from "solid-js";
import { cn } from "~/lib/utils";
export type NewComponentSize = "sm" | "md" | "lg";
export interface NewComponentProps {
size?: NewComponentSize;
class?: string;
children?: JSX.Element;
}
const sizeStyles: Record<NewComponentSize, string> = {
sm: "text-sm px-2 py-1",
md: "text-base px-3 py-2",
lg: "text-lg px-4 py-3",
};
export const NewComponent: Component<NewComponentProps> = (props) => {
const [local, rest] = splitProps(props, ["size", "class", "children"]);
const size = () => local.size ?? "md";
return (
<div class={cn(sizeStyles[size()], local.class)} {...rest}>
{local.children}
</div>
);
};
export default NewComponent;
Key Rules
Styling
- Use CSS variables from
styles/theme.cssfor colors — never hardcode hex values - Use
cn()(from~/lib/utils) for conditional class merging - Support dark mode automatically via CSS variables (
text-foreground,bg-background, etc.) - Size variants (
sm,md,lg) when the component has variable sizing
Accessibility
- Interactive elements need
aria-labelor visible label - Keyboard navigation:
onKeyDownfor Enter/Space on custom buttons - Focus management:
tabindex,focus-visible:styles - Screen reader text:
<span class="sr-only">for icon-only buttons
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 · 98 lines · 0 tokens per session scan A 169fd90de517
frontend-components 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 723 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.