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/column-visibilitynpx skills add TanStack/table --skill column-visibilitygit 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.00048 | $0.00544 |
| Opus 5 | $0.00024 | $0.00272 |
| Sonnet 5 | $0.00010 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
column-visibility 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 yesterday.
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 and table-features. Visibility state changes visibility-aware models; it never removes the column definition.
Setup
import { columnVisibilityFeature, tableFeatures } from '@tanstack/table-core'
export const features = tableFeatures({ columnVisibilityFeature })
export const initialState = { columnVisibility: { internalId: false } }
Core Patterns
const headers = table.getHeaderGroups()
const cells = row.getVisibleCells()
const toggles = table
.getAllLeafColumns()
.filter((column) => column.getCanHide())
Use all-column APIs for controls and visible APIs for rendered table content.
Common Mistakes
[HIGH] Rendering hidden cells anyway
Wrong: row.getAllCells().map(renderCell)
Correct: row.getVisibleCells().map(renderCell)
All-cell APIs intentionally include hidden columns.
Source: docs/framework/react/guide/column-visibility.md#column-visibility-aware-table-apis
[HIGH] Treating absence as hidden
Wrong: const hidden = !columnVisibility[column.id]
Correct: const hidden = columnVisibility[column.id] === false
Only explicit false hides a column; an absent entry is visible.
Source: packages/table-core/src/features/column-visibility/columnVisibilityFeature.ts
[MEDIUM] Treating enableHiding as visibility
Wrong: helper.accessor('id', { enableHiding: false })
Correct: const initialState = { columnVisibility: { id: false } }
enableHiding controls whether hiding is allowed; visibility belongs in table state.
Source: packages/table-core/src/features/column-visibility/columnVisibilityFeature.types.ts
API Discovery
Inspect node_modules/@tanstack/table-core/dist/features/column-visibility/ for visibility-aware table, row, and column 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.
- yesterday First seen · 72 lines · 48 tokens per session scan A 364cb6a60d10
column-visibility is a skill published in the GitHub repository TanStack/table (28,393 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 544 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
grid-lite-to-igr-grid-migration
Step-by-step migration guide from Grid Lite (IgrGridLite) to the premium Ignite UI for React Data Grid (IgrGrid), covering every import, registration, component name, property, event, template, sorting, filtering, and toolbar API change.
igniteui-react-customize-theme
This skill customizes Ignite UI for React component styling using CSS custom properties and the full theming system and should be used when applying brand colors, dark mode, component-level overrides, or scoped themes in a React application.
webgl-expert
Expert guide for WebGL API development including 3D graphics, shaders (GLSL), rendering pipeline, textures, buffers, performance optimization, and canvas rendering. Use when working with WebGL, 3D graphics, canvas rendering, shaders, GPU programming, or when user mentions WebGL, OpenGL ES, GLSL, vertex shaders…
lenis-react
Integrate Lenis smooth scroll into React and Next.js projects. Use when the user wants smooth scrolling, scroll-linked animations, parallax effects, GSAP ScrollTrigger sync, Framer Motion sync, programmatic scroll-to navigation, or scroll event listening in a React app. Covers ReactLenis provider setup, useLenis hook…
gsap-tackl
Implements and orchestrates GSAP in Tackl — useAnimation, useGSAP, ScrollTrigger, Lenis sync, page transitions, and reduced-motion fallbacks. Use when the user mentions GSAP, tweens, timelines, ScrollTrigger, scrub, matchMedia, Lenis, smooth scroll, page transitions, motion design, or enter/exit animations.
tackl-performance
Optimizes Tackl apps for Web Vitals, reduced motion, and scroll performance. Use when the user mentions performance, LCP, CLS, prefers-reduced-motion, lazy loading, scroll jank, or PerformanceContext.