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.
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.
curl -O https://raw.githubusercontent.com/openstatusHQ/data-table-filters/main/AGENTS.mdgit clone --depth 1 https://github.com/openstatusHQ/data-table-filtersWrote 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/instructions/openstatushq/data-table-filters/agents-md)<a href="https://agentmods.dev/instructions/openstatushq/data-table-filters/agents-md"><img src="https://agentmods.dev/badge/instructions/openstatushq/data-table-filters/agents-md/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/instructions/openstatushq/data-table-filters/agents-md"><img src="https://agentmods.dev/badge/instructions/openstatushq/data-table-filters/agents-md.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.01748 | $0.01748 |
| Opus 5.5 | $0.00699 | $0.00699 |
| Sonnet 5.5 | $0.00350 | $0.00350 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
data-table-filters AGENTS.md 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 28d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Two audiences. Pick the section that matches what you're doing.
A. Using data-table-filters in someone's project
What this is: a set of shadcn registry blocks — React components, a schema system, and server-side query helpers — that you copy into the user's repo with the shadcn CLI. It is not an npm dependency. There is nothing to wrap and nothing to eject from; after install, the code belongs to the user.
Stack: React 19+, TanStack Table v8, Tailwind CSS v4, shadcn/ui. Next.js App Router is first-class; the blocks work in any React app.
Prerequisite. Works on either shadcn library: the CLI default, Base UI (
npx shadcn@latest init -d), or Radix (npx shadcn@latest init -b radix -p lyra). CI installs into both and typechecks them on every registry change and nightly. Nothing to check before installing: the blocks resolve their primitives from whichever librarycomponents.jsonnames.
No project yet? One command creates a Next.js app, initializes shadcn, and
installs a working /example route with every block it needs (add -b radix
before -p lyra for Radix); cd logs-viewer, run the dev server and open
http://localhost:3000/example:
pnpm dlx shadcn@latest init @data-table-filters/data-table-example-infinite --name logs-viewer --template next -p lyra
Requires pnpm (npm i -g pnpm); npx and npm run dev work the same if you prefer npm.
Blocks install by name from the shadcn registry directory; the JSON form https://data-table.openstatus.dev/r/<block>.json works too.
Load the full instructions before wiring anything up:
| Resource | What it gives you |
|---|---|
| https://data-table.openstatus.dev/api/mcp | These docs as an MCP server — see below |
| https://data-table.openstatus.dev/llms.txt | Index: blocks, install recipes, docs links |
| https://data-table.openstatus.dev/llms-full.txt | Every documentation page in one file |
| https://data-table.openstatus.dev/r/index.md | Block catalog with install commands and dependencies |
| https://data-table.openstatus.dev/docs/quick-start.md | Any docs page as raw markdown — append .md to the URL |
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.
- 28d ago Changed · +2 lines · +35 tokens per session 96163a304f6c
- 1mo ago Changed · +3 lines · -15 tokens per session 603b7b9c56e1
- 1mo ago Changed · +8 lines · +87 tokens per session fd08a7aba556
- 1mo ago Changed · +30 lines · +430 tokens per session 4fbb621aea95
- 1mo ago First seen · 116 lines · 1,211 tokens per session scan A b32ce8a10cfa
data-table-filters AGENTS.md is an instructions file published in the GitHub repository openstatusHQ/data-table-filters (2,281 stars, last pushed 17d ago), licensed MIT. It adds 1,748 tokens to every session, about $0.0070 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.