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/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/component-update-layout)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-layout"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-layout/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/oakensoul/nextjs-cursor-prompts/component-update-layout"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-layout.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.05558 |
| Opus 5.5 | $0.00000 | $0.02223 |
| Sonnet 5.5 | $0.00000 | $0.01112 |
| Haiku 4.5 | $0.00000 | $0.00556 |
Grade A, and why
component-update-layout 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 2mo 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 — 840 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layout Component Update Request
Please update and enhance an existing layout component following our responsive design improvement patterns and performance standards:
🎯 LAYOUT COMPONENT UPDATE OBJECTIVES:
- ENHANCE responsive design with improved breakpoint handling, container queries, and mobile optimization
- IMPROVE performance with optimized rendering, layout stability, and resource efficiency
- UPGRADE accessibility with better landmark structure, focus management, and screen reader navigation
- OPTIMIZE composition patterns with flexible slots, better content organization, and reusable patterns
- MAINTAIN backward compatibility while implementing meaningful layout and architectural improvements
📋 LAYOUT UPDATE METHODOLOGY:
STEP 1: Current Layout Assessment
Analyze Existing Implementation:
- Responsive behavior: Test layout across all breakpoints and device orientations
- Performance metrics: Measure Cumulative Layout Shift (CLS) and rendering performance
- Accessibility audit: Check landmarks, heading hierarchy, and navigation patterns
- Composition flexibility: Evaluate slot system and content organization capabilities
- NextJS integration: Review app router compatibility and server component optimization
Identify Enhancement Opportunities:
// Assessment checklist for layout improvements
interface LayoutComponentAudit {
responsiveDesign: {
mobileFirst: boolean;
breakpointConsistency: boolean;
containerQueries: boolean;
touchOptimization: boolean;
};
performance: {
layoutStability: boolean;
renderingSpeed: boolean;
bundleSize: boolean;
memoryEfficiency: boolean;
};
accessibility: {
landmarks: boolean;
headingHierarchy: boolean;
skipLinks: boolean;
focusManagement: boolean;
};
composition: {
flexibleSlots: boolean;
reusablePatterns: boolean;
contentOrganization: boolean;
dynamicLayout: boolean;
};
}
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.
- 2mo ago First seen · 840 lines · 0 tokens per session scan A 52248c813f61
component-update-layout is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,558 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
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
frontend-design-direction
Derive a brief-specific visual direction, token sketch, hierarchy, and signature element.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.