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/ninsau/nextjs-reusable-table/typesgit clone --depth 1 https://github.com/ninsau/nextjs-reusable-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.00000 | $0.00442 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
types 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
Type Definition Rules
All Interfaces Live in src/types/index.ts
Never define props interfaces inside component files. All public-facing types are exported from src/types/index.ts and re-exported via src/index.ts with export * from "./types".
Interface Naming
- Table component props:
TableProps<T> - Sub-component props:
ActionDropdownProps<T>,PaginationComponentProps,TableSkeletonProps,NoContentProps - Internal helpers: prefix with
Ior suffix withConfig(e.g.,CellExpansionConfig)
Generic Constraints
// Always use T for row data — never object or any
interface TableProps<T> {
data: T[];
props: ReadonlyArray<keyof T>; // keyof T enforces type-safe column access
sortableProps?: Array<keyof T>;
formatValue?: (value: string, prop: string, item: T) => React.ReactNode;
}
Optional Props with Nested Objects
Group related optional config into named nested objects:
cellExpansion?: {
enabled?: boolean;
maxWidth?: string | number;
behavior?: "truncate" | "wrap" | "expand";
};
accessibility?: {
keyboardNavigation?: boolean;
screenReaderLabels?: { actions?: string; pagination?: string; loading?: string };
};
customClassNames Shape
The customClassNames prop mirrors the DOM structure of the rendered table.
Every element the consumer might want to style has its own key.
New styled elements added to components MUST get a corresponding key in TableProps["customClassNames"].
No any
Biome enforces noExplicitAny: "error". Use:
unknownfor truly unknown values, then narrow with type guardsReact.ReactNodefor renderable contentRecord<string, boolean>for string-keyed boolean maps
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 · 52 lines · 0 tokens per session scan A bb0a1aaf2f1b
types is a cursor rule published in the GitHub repository ninsau/nextjs-reusable-table (6 stars, last pushed 5mo ago), licensed 0BSD. It costs nothing until one of its globs matches a file; then it loads 442 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
java-import-fqn
Java 禁止不必要的全限定类名,必须 import(类名冲突除外).
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.