data-display-and-selection

data-display-and-selection is a skill for Claude Code from dembrandt/dembrandt-skills. It costs 37 tokens per session (4,569 once invoked), scanned A, original, MIT.

A user-interface guide for displaying collections of data as grids, lists, or tables and letting people select rows or items. It explains which view fits browsing, detail comparison, or bulk management.

In plain words
What is it for?
Use it when designing collection screens with view switching, filtering, sorting, large selection areas, selected-state feedback, and bulk actions.
Why use it?
It helps users work with products, files, orders, users, or tasks without forcing every job into one layout.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dembrandt plugin — 45 skills, 1 MCP server shipped together

Good fit Use it when designing collection screens with view switching, filtering, sorting, large selection areas, selected-state feedback, and bulk actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dembrandt/dembrandt-skills/data-display-and-selection
Install

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.

Any agent
npx skills add dembrandt/dembrandt-skills --skill data-display-and-selection
Clone the repo
git clone --depth 1 https://github.com/dembrandt/dembrandt-skills

Made for: Claude Code.

Or install dembrandt, the plugin that ships this one along with the rest of its 45 skills, 1 MCP server.

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 data-display-and-selection

README.md
[![agentmods](https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/data-display-and-selection/github.svg)](https://agentmods.dev/skills/dembrandt/dembrandt-skills/data-display-and-selection)
Your own site
<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/data-display-and-selection"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/data-display-and-selection/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.

agentmods 80×15 button for data-display-and-selection

Your own site · 80×15
<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/data-display-and-selection"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/data-display-and-selection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,569 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. Third-party audits
  • Socket pass 2 Oct 2026
  • Snyk pass 2 Oct 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00037 $0.04569
Opus 5.5 $0.00015 $0.01828
Sonnet 5.5 $0.00007 $0.00914
Haiku 4.5 $0.00004 $0.00457

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

Security

Grade A, and why

data-display-and-selection 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 19d 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.

skills/data-display-and-selection/SKILL.md · 313 lines

How it starts

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

Data Display and Selection

Complex data collections — products, files, users, orders, tasks — have no single correct view. Different tasks call for different views. Browsing benefits from grid; comparing details benefits from list or table; bulk management benefits from a dense table with mass actions. Give users the choice.


View Modes

Offer multiple views when the data has both visual and detailed dimensions.

View Best for When to default
Grid Visual items: products, images, files, cards When items are visually distinct and browsing is the primary task
List Moderate detail: tasks, emails, articles When a key piece of text or metadata drives selection
Table Dense data: orders, reports, user management When multiple columns of data must be compared

View toggle placement: top-right of the collection, adjacent to sort/filter controls. Use icon buttons with tooltips (grid, list, table). Persist the user's choice in localStorage.

[Filter ▾]  [Sort ▾]          [⊞ Grid]  [☰ List]  [⊟ Table]

On mobile, collapse to the view that works best for the content — grid for visual items, list for text. Do not offer a view toggle on small screens unless both views are genuinely usable.

Past a Handful of Items, Cards Become a Table

A card earns its border when it is one of a few things a reader compares side by side. Repeat that border fifteen times down a page and it separates nothing: every row is boxed, so the boxes carry no information and the reader pays for them in noise.

Past roughly six items, drop to a table. Keep a horizontal rule between rows or stripe them, and drop the side and outer rules entirely. Vertical edges do no work in a list already bounded by the page's own column, and the eye groups by proximity and alignment long before it needs a drawn line.

The exception is a card that contains something a row cannot. An image, a chart, a per-item control set, a body of text that has to wrap: those keep their card at any count, because the border is holding a composition together rather than separating one line from the next. A product grid, a gallery, a set of dashboard tiles are not covered by this rule. The test is what the border encloses. If it encloses a line of text and a value, it is decoration on a table row. If it encloses a layout, it is a card.

Read the full file on GitHub · 313 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. 19d ago Changed · +29 lines f75fcb56d961
  2. 26d ago Changed · +6 lines · -48 tokens per session 70545362a6c0
  3. 1mo ago Changed · +2 lines da3d30246b9f
  4. 1mo ago Changed · +18 lines 36b9121f7418
  5. 1mo ago First seen · 258 lines · 85 tokens per session scan A 03fe7c375b08

Subscribe to this mod's changes

data-display-and-selection is a skill published in the GitHub repository dembrandt/dembrandt-skills (169 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 4,569 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

design-dna

Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…

zanwei/design-dna · 192 tokens

dbim-brand-identity

Use when applying the Government of India's Digital Brand Identity Manual (DBIM) v3 to a website, portal, form, mobile app or social media asset — colours, Noto Sans typography, State Emblem logo lockups, header/footer anatomy, imagery specs, content lifecycle and the compliance checklist. Triggers include "DBIM"…

Yashraj00700/indian-gov-ui-skills · 117 tokens

indian-gov-web-ui

A set of design and accessibility rules for Indian government websites, portals, and administrative panels, including required standards such as GIGW and WCAG.

Yashraj00700/indian-gov-ui-skills · 95 tokens

ux4g-design-system

Use when building or reviewing UI with UX4G — India's official government design system (ux4g.gov.in, cdn.ux4g.gov.in, ux4g-web-components). Covers the v3.0.18 token API, the 52 components, install paths for HTML/React/Angular/Flutter, and the interop hazards. Triggers include "UX4G", "ux4g-web-components"…

Yashraj00700/indian-gov-ui-skills · 147 tokens

gov-service-patterns

Use when designing or building a citizen-facing government service flow — sign-in/OTP/Aadhaar authentication, consent and declaration, multi-step application submission, application/grievance status tracking, fee payment, service search and slot booking, citizen or officer dashboards, notifications, or feedback and…

Yashraj00700/indian-gov-ui-skills · 115 tokens

ui-ux-laws

Priority-ordered rulebook of core UX/UI laws, cognitive-psychology principles, Nielsen's usability heuristics, and accessibility requirements that Claude must actively apply (not just cite) whenever it designs, builds, redesigns, reviews, or critiques any user interface — websites, web/mobile apps, dashboards, forms…

AmirGhl/ui-ux-laws · 203 tokens