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/oakensoul/nextjs-cursor-prompts/component-update-navigationgit 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-navigation)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-navigation"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-navigation.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.1 | $0.00000 | $0.03879 |
| Opus 5 | $0.00000 | $0.01939 |
| Sonnet 5 | $0.00000 | $0.00776 |
| Haiku 4.5 | $0.00000 | $0.00388 |
Grade A, and why
component-update-navigation 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 — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigation Component Update Request
Please enhance the existing navigation component with performance optimizations, accessibility improvements, mobile experience upgrades, and advanced navigation features.
🎯 NAVIGATION UPDATE OBJECTIVES:
- OPTIMIZE performance with efficient rendering, lazy loading, and state management improvements
- ENHANCE accessibility with advanced ARIA patterns, keyboard navigation, and screen reader support
- IMPROVE mobile experience with touch interactions, responsive patterns, and progressive enhancement
- ADD advanced features like analytics integration, dynamic navigation, and user preferences
- MAINTAIN backward compatibility while implementing modern navigation patterns
📋 NAVIGATION ENHANCEMENT METHODOLOGY:
STEP 1: Current Navigation Assessment
Performance Analysis:
- Rendering efficiency: Identify unnecessary re-renders and optimization opportunities
- Bundle size impact: Analyze navigation component size and lazy loading potential
- State management: Review current state patterns and optimization opportunities
- Memory usage: Check for memory leaks in navigation interactions
Accessibility Audit:
- WCAG compliance: Verify current WCAG 2.1 AA compliance level
- Keyboard navigation: Test comprehensive keyboard accessibility
- Screen reader compatibility: Validate screen reader announcements and navigation
- Focus management: Review focus indicators and logical tab order
Mobile Experience Review:
- Touch target sizing: Ensure minimum 44px touch targets
- Responsive behavior: Test navigation across different screen sizes
- Performance on mobile: Analyze mobile-specific performance issues
- Gesture support: Evaluate touch gesture implementation
STEP 2: Performance Optimization Strategies
Rendering Optimization:
// Memoized navigation component for performance
const NavigationComponent = memo(({ items, currentPath, ...props }) => {
// Memoize active state calculations
const activeStates = useMemo(() =>
calculateActiveStates(items, currentPath),
[items, currentPath]
)
// Memoize navigation items with stable references
const memoizedItems = useMemo(() =>
items.map(item => ({
...item,
isActive: activeStates[item.href],
children: item.children?.map(child => ({
...child,
isActive: activeStates[child.href]
}))
})),
[items, activeStates]
)
return (
<NavigationContainer
items={memoizedItems}
{...props}
/>
)
})
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 · 602 lines · 0 tokens per session scan A df70acda514a
component-update-navigation 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 3,879 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.