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/jakerains/citrusrules/component-standardsgit clone --depth 1 https://github.com/jakerains/CitrusRulesWhat 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.00288 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
component-standards 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 2d 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
name: ComponentStandards type: Auto Attached description: Enforce structure, naming, and styling rules for UI components across frameworks glob: **/*.{jsx,tsx,vue,svelte} priority: high
Component Development Standards
Follow these conventions for all components.
Naming and Organization
- Use PascalCase for component names.
- Keep each component in its own folder with
indexexport. - Group related style files alongside the component.
Reusability Principles
- Keep components small and focused on a single responsibility.
- Accept props with explicit types and default values.
- Avoid side effects in rendering logic.
Styling Guidelines
- Prefer CSS-in-JS or scoped styles to avoid global leakage.
- Keep class names predictable and use BEM when applicable.
- Co-locate styles with components.
Example
// Example React functional component
export interface ButtonProps {
label: string;
onClick?: () => void;
}
export function Button({ label, onClick }: ButtonProps) {
return (
<button className="btn" onClick={onClick}>
{label}
</button>
);
}
This template ensures consistency and reusability across your component library.
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.
- 2d ago First seen · 55 lines · 0 tokens per session scan A a50aaf7a29cb
component-standards is a cursor rule published in the GitHub repository jakerains/CitrusRules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 288 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.