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/verdikta/verdikta-applications/frontend-patternsgit clone --depth 1 https://github.com/verdikta/verdikta-applicationsWrote 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/verdikta/verdikta-applications/frontend-patterns)<a href="https://agentmods.dev/rules/verdikta/verdikta-applications/frontend-patterns"><img src="https://agentmods.dev/badge/rules/verdikta/verdikta-applications/frontend-patterns.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.01749 |
| Opus 5 | $0.00000 | $0.00874 |
| Sonnet 5 | $0.00000 | $0.00350 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
frontend-patterns scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const result = await axios.post('/api/jobs/create', jobData); How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Patterns
Component Structure
Standard Component Layout
import { useState, useEffect } from 'react';
import { useParams, useNavigate } from 'react-router-dom';
import { apiService } from '../services/api';
import './ComponentName.css';
function ComponentName({ walletState }) {
// State
const [data, setData] = useState(null);
const [loading, setLoading] = useState(false);
const [error, setError] = useState(null);
// Hooks
const { id } = useParams();
const navigate = useNavigate();
// Effects
useEffect(() => {
loadData();
}, [id]);
// Handlers
const handleAction = async () => {
try {
setLoading(true);
setError(null);
// ... operation
} catch (err) {
setError(err.message);
} finally {
setLoading(false);
}
};
// Render helpers
if (loading) return <LoadingState />;
if (error) return <ErrorState error={error} />;
return (
<div className="component-name">
{/* Content */}
</div>
);
}
export default ComponentName;
State Management
Loading States
Always show loading indicators:
const [loading, setLoading] = useState(false);
{loading && (
<div className="loading-status">
<div className="spinner"></div>
<p>Processing...</p>
</div>
)}
Error Handling
Display user-friendly errors:
const [error, setError] = useState(null);
{error && (
<div className="alert alert-error">
<p>❌ {error}</p>
</div>
)}
Form Validation
Validate on both change and submit:
const handleInputChange = (e) => {
const value = e.target.value;
// Real-time validation
if (value.length > MAX_LENGTH) return;
setValue(value);
setError(null);
};
const handleSubmit = async (e) => {
e.preventDefault();
// Pre-submit validation
if (!value.trim()) {
alert('Field is required');
return;
}
// Submit
};
API Integration
Use API Service Layer
Never use axios directly in components:
// ✅ Good
const result = await apiService.createJob(jobData);
// ❌ Bad
const result = await axios.post('/api/jobs/create', jobData);
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.
- 4d ago First seen · 340 lines · 1,749 tokens per session scan A 3240381ab3c8
frontend-patterns is a cursor rule published in the GitHub repository verdikta/verdikta-applications (24 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,749 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
backend
Backend development rules for TT Studio - AI model management backend.
new-component
Workflow for creating new React components.
trove-react
React 19 coding conventions and performance patterns. Auto-activates when working with React/TypeScript files. Covers hooks, state management, TanStack Query, Zustand, immutable updates, and component conventions.
component-patterns
React Component Patterns.