data-table-filters: Skill for Claude Code

.agents/skills/next-best-practices/SKILL.md

next-best-practices is a skill for Claude Code from openstatusHQ/data-table-filters. It costs 38 tokens per session (1,017 once invoked), scanned A, a copy of next-best-practices, MIT.

Guidance for building and reviewing Next.js applications, covering file conventions, server and client component boundaries, asynchronous APIs, runtime choices, metadata, errors, routing, and optimisation.

In plain words
What is it for?
Use it when creating or reviewing Next.js routes, components, server functions, metadata, middleware or proxy code, error handling, images, fonts, and application structure.
Why use it?
It helps catch framework-specific mistakes, especially around newer asynchronous APIs and deciding which code runs on the server or in the browser.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is openstatusHQ/data-table-filters's own configuration. It tells Claude Code how to work on data-table-filters itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything data-table-filters configures →

Part of the data-table-filters plugin — 15 skills, 1 hook, 2 MCP servers shipped together

About the project

openstatusHQ/data-table-filters is a React toolkit for building data tables with filters, sorting, scrolling, and reusable table components. It helps developers create filterable tables using shadcn/ui and TanStack Table. The catalogue add-ons provide table blocks, state adapters, cell renderers, query integration, and other parts of its workflow.

openstatusHQ/data-table-filters · 2,226 stars · on GitHub · logs.run

Reuse

Borrowing it

Nothing to install: this file belongs to openstatusHQ/data-table-filters. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/openstatusHQ/data-table-filters/main/.agents/skills/next-best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/openstatusHQ/data-table-filters

Made for: Claude Code.

Or install data-table-filters, the plugin that ships this one along with the rest of its 15 skills, 1 hook, 2 MCP servers.

Wrote 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.

agentmods badge for next-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/openstatushq/data-table-filters/next-best-practices.svg)](https://agentmods.dev/skills/openstatushq/data-table-filters/next-best-practices)
Your own site
<a href="https://agentmods.dev/skills/openstatushq/data-table-filters/next-best-practices"><img src="https://agentmods.dev/badge/skills/openstatushq/data-table-filters/next-best-practices.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,017 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01017
Opus 5 $0.00019 $0.00508
Sonnet 5 $0.00008 $0.00203
Haiku 4.5 $0.00004 $0.00102

Measured 8d ago against content hash dd00692365ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

next-best-practices 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 8d 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.

Origin

This is a copy

100% identical to next-best-practices — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/next-best-practices/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Next.js Best Practices

Apply these rules when writing or reviewing Next.js code.

File Conventions

See file-conventions.md for:

  • Project structure and special files
  • Route segments (dynamic, catch-all, groups)
  • Parallel and intercepting routes
  • Middleware rename in v16 (middleware → proxy)

RSC Boundaries

Detect invalid React Server Component patterns.

See rsc-boundaries.md for:

  • Async client component detection (invalid)
  • Non-serializable props detection
  • Server Action exceptions

Async Patterns

Next.js 15+ async API changes.

See async-patterns.md for:

  • Async params and searchParams
  • Async cookies() and headers()
  • Migration codemod

Runtime Selection

See runtime-selection.md for:

  • Default to Node.js runtime
  • When Edge runtime is appropriate

Directives

See directives.md for:

  • 'use client', 'use server' (React)
  • 'use cache' (Next.js)

Functions

See functions.md for:

  • Navigation hooks: useRouter, usePathname, useSearchParams, useParams
  • Server functions: cookies, headers, draftMode, after
  • Generate functions: generateStaticParams, generateMetadata

Error Handling

See error-handling.md for:

  • error.tsx, global-error.tsx, not-found.tsx
  • redirect, permanentRedirect, notFound
  • forbidden, unauthorized (auth errors)
  • unstable_rethrow for catch blocks

Data Patterns

See data-patterns.md for:

  • Server Components vs Server Actions vs Route Handlers
  • Avoiding data waterfalls (Promise.all, Suspense, preload)
  • Client component data fetching

Route Handlers

See route-handlers.md for:

  • route.ts basics
  • GET handler conflicts with page.tsx
  • Environment behavior (no React DOM)
  • When to use vs Server Actions

Metadata & OG Images

See metadata.md for:

Read the full file on GitHub · 172 lines

Changes

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.

  1. 8d ago First seen · 172 lines · 38 tokens per session scan A dd00692365ff

Subscribe to this mod's changes

next-best-practices is a skill published in the GitHub repository openstatusHQ/data-table-filters (2,226 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,017 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to next-best-practices, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

coss-particles

Index of all COSS UI particle examples. Use when implementing UI features to find copy-paste-ready component patterns built on coss primitives. Each particle has a description and a JSON URL for easy installation.

cosscom/coss · 46 tokens

coss

Helps implement coss UI components correctly. Use when building UIs with coss primitives and patterns (buttons, dialogs, selects, forms, menus, tabs, segmented controls, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior.…

cosscom/coss · 85 tokens

migrate-radix-to-base

Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.

shadcn-ui/ui · 61 tokens

copilotkit-integrations

Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.

CopilotKit/CopilotKit · 61 tokens

nextjs-app-router

Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.

trpc/trpc · 74 tokens

nextjs-pages-router

Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.

trpc/trpc · 67 tokens