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 skills/tanstack/table/paginationnpx skills add TanStack/table --skill paginationgit clone --depth 1 https://github.com/TanStack/tableWhat 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.00049 | $0.00584 |
| Opus 5 | $0.00024 | $0.00292 |
| Sonnet 5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
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 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
This skill builds on core, table-features, and client-vs-server. Choose client slicing or server pages, never both accidentally.
Setup
import {
createPaginatedRowModel,
rowPaginationFeature,
tableFeatures,
} from '@tanstack/table-core'
export const features = tableFeatures({
rowPaginationFeature,
paginatedRowModel: createPaginatedRowModel(),
})
export const initialState = { pagination: { pageIndex: 0, pageSize: 25 } }
Core Patterns
const serverOptions = { manualPagination: true, rowCount: response.total }
Pass one already-processed page and either rowCount or pageCount.
Common Mistakes
[CRITICAL] Expecting manual mode to slice
Wrong: const options = { data: allRows, manualPagination: true }
Correct: const options = { data: requestedPageRows, manualPagination: true, rowCount: totalRows }
Manual pagination trusts the provided data as the current page.
Source: https://github.com/TanStack/table/issues/4917
[HIGH] Omitting the server total
Wrong: const options = { data: pageRows, manualPagination: true }
Correct: const options = { data: pageRows, manualPagination: true, rowCount: 1234 }
Without a count, last-page and next-page availability cannot reflect the server dataset.
Source: packages/table-core/src/features/row-pagination/rowPaginationFeature.types.ts
[HIGH] Fighting automatic page resets
Wrong: onPaginationChange: setPagination
Correct: const options = { onPaginationChange: setPagination, autoResetPageIndex: false }
Client data and processing changes may reset page index; configure the policy when product state must retain it.
Source: docs/framework/react/guide/pagination.md#auto-reset-page-index
API Discovery
Inspect node_modules/@tanstack/table-core/dist/features/row-pagination/ for reset rules, count calculation, and navigation APIs.
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 · 75 lines · 49 tokens per session scan A 38aa7267d85f
pagination is a skill published in the GitHub repository TanStack/table (28,393 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 584 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other skills, from other repositories
gsap-performance
Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-rspack
Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack crate versions, Rust toolchain version, building and linking for…
next-dev-loop
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running next dev.
flow
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
react-grab
Use when the user wants a hands-free loop where grabbing UI elements in the browser with React Grab feeds tasks to the agent automatically, with no copy-paste or manual handoff. Triggers: "watch react grab", "monitor my grabs", "auto-process react grab", "watch my clipboard for grabs". Not for a one-off paste of a…