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/lsampaioweb/ai-instructions/spring-boot-paginationgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/spring-boot-pagination)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-pagination"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-pagination.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.00597 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
spring-boot-pagination 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Pagination Engine
Rules
- Treat every REST GET collection endpoint as paginated by default.
- Use Spring Data
Pageableas the default pagination strategy for collection endpoints. - Use custom validated
page/sizeparameters only when Spring Data integration is not available. - Require an explicit documented exception before using a non-paginated GET collection endpoint.
- When a non-paginated GET collection endpoint is explicitly approved, define and enforce a deterministic server-side result limit.
- Apply
@Min(0)to thepage@RequestParamand@Positiveto thesize@RequestParamwhen using custom pagination. - Declare
Pageableas a direct controller method parameter for paginated endpoints. - Store pagination defaults and limits in configuration properties, not in controller classes.
- Use
spring.data.web.pageableproperties for Spring DataPageabledefaults. - Use typed
@ConfigurationProperties(e.g.,app.pagination.*) for custom pagination defaults and limits. - Configure
page=0,size=20, andmax=100as the definitive pagination defaults inspring.data.web.pageableorapp.pagination.*properties. - Return paged responses that include
content,totalElements,totalPages,page, andsizefields. - Map Spring's
Page<T>to a stable custom*PageResponseDTO before returning it from any endpoint. - Use zero-based page numbering.
- Document zero-based page numbering explicitly in OpenAPI annotations for every paginated endpoint.
- Use ascending sort by a stable resource key as the default sort order for paginated endpoints.
- Accept sort via a
sortrequest parameter infield,asc|descformat when using custom pagination. - Declare an explicit allowlist of valid sort field names for each paginated endpoint.
- Reject unknown sort fields with HTTP 400.
- Enforce a max-page-size limit when custom pagination configuration exists.
- Validate custom
page/sizeconstraints in the service layer once per use case. - Normalize out-of-range pagination inputs: clamp
pageto0if negative andsizeto1if zero or negative. - Return an empty
contentlist with correct total-count metadata when the requested page exceeds the total number of available pages. - Extract shared pagination link-building logic into a single utility class in the
sharedpackage when the same structure is used by two or more features.
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 · 37 lines · 0 tokens per session scan A e49188220618
spring-boot-pagination is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 597 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.