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/aiagentwithdhruv/ai-dev-stack/20-frontend-nextjsgit clone --depth 1 https://github.com/aiagentwithdhruv/ai-dev-stackWhat 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.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
20-frontend-nextjs 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
Frontend stack:
- Next.js
- TypeScript
- Component-driven UI
- API integration with backend services
Frontend rules:
- Prefer TypeScript for all frontend logic.
- Keep components small, reusable, and focused.
- Keep presentation separate from business/data-fetching logic.
- Use hooks, services, or server actions appropriately based on project style.
- Handle loading, error, and empty states explicitly.
- Preserve design consistency and naming consistency.
Preferred frontend structure:
- frontend/app/
- frontend/components/
- frontend/features/
- frontend/hooks/
- frontend/lib/
- frontend/services/
- frontend/types/
- frontend/tests/
UI/UX rules:
- Use accessible markup and semantic HTML.
- Prefer reusable design system components.
- Avoid oversized page components.
- Avoid embedding complex API logic directly inside visual components unless already established in the repo.
State/data rules:
- Keep API clients centralized.
- Normalize repeated API access patterns.
- Handle auth state carefully.
- Validate critical inputs on both client and server.
Do not:
- Mix many responsibilities into one component.
- Hardcode API URLs in components.
- Duplicate UI patterns that should be shared.
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 · 46 lines · 0 tokens per session scan A 80fe5088f37b
20-frontend-nextjs is a cursor rule published in the GitHub repository aiagentwithdhruv/ai-dev-stack (10 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 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
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
cursorrules
Code exhibits taste — Torvalds' term for finding the formulation where special cases disappear. Seek representations where edge cases become impossible, the type system proves correctness, and the API guides users into the pit of success.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.
cross-tool-config
Cross-tool AI config: what transfers between Cursor, Claude Code, Copilot, Windsurf, Gemini, and Codex.