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/lacymorrow/paperclip-hubWrote 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/lacymorrow/paperclip-hub/nextjs)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/nextjs"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/nextjs/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/lacymorrow/paperclip-hub/nextjs"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/nextjs.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.00619 |
| Opus 5.5 | $0.00000 | $0.00248 |
| Sonnet 5.5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
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 yesterday.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Best Practices
params should be awaited before using its properties.
searchParams should be awaited before using its properties.
headers should be awaited before using its properties.
Server Components
- Use Server Components by default
- Keep client components minimal
- Don't nest server in client components
- Use proper data fetching patterns
- Implement proper caching strategies
- Handle streaming and suspense
- Consider SEO implications
Data Fetching
- Use Server Components for data fetching
- Don't fetch data in Server Actions
- Implement proper caching
- Handle loading states
- Consider revalidation strategies
- Use proper error boundaries
- Optimize for performance
Server Actions
- Use for data mutations only
- Keep business logic in services
- Implement proper validation
- Handle errors gracefully
- Use proper typing
- Consider optimistic updates
- Document side effects
Routing
- Use App Router
- Implement proper layouts
- Handle dynamic routes properly
- Use proper loading UI
- Implement error boundaries
- Consider parallel routes
- Handle intercepting routes
State Management
- Use Server Components when possible
- Keep client state minimal
- Use hooks appropriately
- Implement proper caching
- Consider server state
- Handle revalidation
- Document state flow
Performance
- Use proper image optimization
- Implement proper caching
- Consider bundle size
- Use proper code splitting
- Implement proper loading states
- Monitor performance metrics
- Optimize for Core Web Vitals
Security
- Implement proper authentication
- Use proper authorization
- Handle CSRF protection
- Implement proper headers
- Use environment variables
- Handle sensitive data
- Regular security audits
Error Handling
- Use error boundaries
- Implement proper logging
- Handle API errors
- Consider recovery strategies
- Document error scenarios
- Monitor error rates
- Implement proper fallbacks
Testing
- Test Server Components
- Test Server Actions
- Implement E2E tests
- Consider integration tests
- Test error scenarios
- Monitor test coverage
- Document test strategy
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.
- yesterday First seen · 120 lines · 619 tokens per session scan A 38e47f1a8f5a
nextjs is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 619 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-11-10.
nextjs compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| nextjslacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| always-push-pritsmemeworks/adhx | Cursor rule | 19 | 5d ago | MIT | A | 279 | Cursor |
| codex-premium-website-skillsTheGoat395/Codex-Skills | Cursor rule | 137 | 20d ago | MIT | A | 0 | Cursor |
| context-managementvibestackdev/vibe-stack | Cursor rule | 8 | yesterday | MIT | A | 0 | Cursor |
| project-contextvibestackdev/vibe-stack | Cursor rule | 8 | yesterday | MIT | A | 508 | Cursor |
| typescript-coding-styleWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 128 | Cursor |
| javascript-typescript-code-styleWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 88 | Cursor |